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
This article, discusses a more modern way to configure our package dependencies:
By introducing npm local paths, a lot of Lerna complex commands are no longer necessary to use. Plain old npm install suffice to setup the entire monorepo
Part 1 of this would be to update the dependencies in the package.json file for each package (for example here) per this example:
The next step would be to update the main package.json file to reference all the packages per this example:
Finally, after all these changes, we can now remove the lerna bootstrap step from the postinstall script since it's no longer necessary.
Just throwing this out there for initial feedback and comments. It seems like doing this is now the "more proper" way to do things, and in theory might speed up the npm install process.
The text was updated successfully, but these errors were encountered:
I think #911 cleans things up in a different way, using the workspaces stuff, so let's close this for now and come back to it after the dust settles from the next major release if it still is applicable.
This article, discusses a more modern way to configure our package dependencies:
Part 1 of this would be to update the dependencies in the
package.json
file for each package (for example here) per this example:The next step would be to update the main
package.json
file to reference all the packages per this example:Finally, after all these changes, we can now remove the
lerna bootstrap
step from thepostinstall
script since it's no longer necessary.Just throwing this out there for initial feedback and comments. It seems like doing this is now the "more proper" way to do things, and in theory might speed up the
npm install
process.The text was updated successfully, but these errors were encountered: