Idea: separate npm/yarn/pnpm/lerna package managers #4093
Labels
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
type:refactor
Refactoring or improving of existing code
The existing "npm" manager in Renovate is really complex, partly due to its combination of npm/pnpm/yarn/lerna. I wonder if it would be feasible to separate them into separate package managers, albeit with a lot of shared code.
npm - if
package-lock.json
ornpm-shrinkwrap.json
are present, or no other managers are present (i.e. it's the default)yarn - if
yarn.lock
is present. But not if there's lerna?pnpm - look for pnpm's lock files
lerna - does it take precedence over yarn workspaces, or does yarn workspaces mean we can ignore lerna?
The text was updated successfully, but these errors were encountered: