You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also has the advantage that one could properly declare dependencies (e.g. currently one has prop-types as peer dependency, but this is react-specific). (You don't have to split the repository, one common mono-repo approach is to have a packages folder, with each package being a subfolder there, i.e. packages/vue, packages/react and packages/core.)
I have to admit that I don't have any experience with this myself. But based on what I've seen, you can start with yarn workspaces and setup publishing etc yourself. Or use build tools such as https://lerna.js.org/ which add additional convenience on top of workspaces.
Currently, the vue and react parts are simply exported to
dist
which makes for rather awkward imports such asInstead, I would propose to create new packages that encapsulate these. So for example, one could have
Also has the advantage that one could properly declare dependencies (e.g. currently one has prop-types as peer dependency, but this is react-specific). (You don't have to split the repository, one common mono-repo approach is to have a
packages
folder, with each package being a subfolder there, i.e.packages/vue
,packages/react
andpackages/core
.)This was triggered by DefinitelyTyped/DefinitelyTyped#62368 (comment)
The text was updated successfully, but these errors were encountered: