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
Does npm workspaces help or bring more issues with package scopes?
With lerna I always have issues with package scoping. Adding dev dependencies at root means you can't execute them in the package folder etc. Quasar project dependencies at root also caused a loot of issues when trying to build the quasar projects. Does npm workspaces bring new issues or will the fact that all packages are in a single node_modules folder at root be helpful.
does npm workspaces replace lerna?
Besides symlinking local packages to each other, lerna has the benefit of lerna deploy, which automatically increments all package versions throughout the local versions and dependencies, and automatically adds a "tag" with that version number on Github.
Is NPM Workspaces to be used WITH lerna, or maybe we don't need lerna anymore since we're changing the whole CI pipeline anyway?
The text was updated successfully, but these errors were encountered:
develop on
dev
branch -- makedev
the "main" branchwishes for CI
production
(or even todev
) to run automated testsproduction
if automated tests passedrelated
open questions
Does npm workspaces help or bring more issues with package scopes?
With lerna I always have issues with package scoping. Adding dev dependencies at root means you can't execute them in the package folder etc. Quasar project dependencies at root also caused a loot of issues when trying to build the quasar projects. Does npm workspaces bring new issues or will the fact that all packages are in a single node_modules folder at root be helpful.
does npm workspaces replace lerna?
Besides symlinking local packages to each other, lerna has the benefit of
lerna deploy
, which automatically increments all package versions throughout the local versions and dependencies, and automatically adds a "tag" with that version number on Github.Is NPM Workspaces to be used WITH lerna, or maybe we don't need lerna anymore since we're changing the whole CI pipeline anyway?
The text was updated successfully, but these errors were encountered: