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
npm supports workspaces, and we can initiate a command from the root which executes a command in each package (package-one, package-two, etc) based on the command as defined in that child's package.json
other libs (ex tsup) have monorepo with workspaces support by specifying a path to the config file via cli. so our child repo package.jsons can refer to a source config.rc file in the root without copying the config file to every single child repo.
Current Behavior
running the npm-check from the root via workspaces ignores the config defined at the root, and there is no way to override the depcheck config value via cli. this means copying the .npmcheckrc file 20+ however many times which is tedious in a large monorepo
Expected Behavior
add a config argument that lets us set a path to the config file. in monorepos like ours it would be npx npm-check --config ../../.npmcheckrc
The text was updated successfully, but these errors were encountered:
RachelScodes
changed the title
MOnorepo support via config path specification
Monorepo/workspaces support via config path specification CLI arg
May 3, 2024
npm-check-updates
node >= 14.14
Steps to Reproduce
construct a monorepo, with structure like so:
npm supports workspaces, and we can initiate a command from the root which executes a command in each package (package-one, package-two, etc) based on the command as defined in that child's package.json
other libs (ex tsup) have monorepo with workspaces support by specifying a path to the config file via cli. so our child repo package.jsons can refer to a source config.rc file in the root without copying the config file to every single child repo.
Current Behavior
running the npm-check from the root via workspaces ignores the config defined at the root, and there is no way to override the depcheck config value via cli. this means copying the .npmcheckrc file 20+ however many times which is tedious in a large monorepo
Expected Behavior
add a config argument that lets us set a path to the config file. in monorepos like ours it would be
npx npm-check --config ../../.npmcheckrc
The text was updated successfully, but these errors were encountered: