Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monorepo/workspaces support via config path specification CLI arg #1405

Open
3 tasks done
RachelScodes opened this issue May 3, 2024 · 1 comment
Open
3 tasks done

Comments

@RachelScodes
Copy link

  • I have searched for similar issues
  • I am using the latest version of npm-check-updates
  • I am using node >= 14.14

Steps to Reproduce

construct a monorepo, with structure like so:

/root
 - package.json
 - .npmcheckrc
 - /packages
   - /package-one
     - package.json
   - /package-two
     - package.json
   - /etc...

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

@RachelScodes RachelScodes changed the title MOnorepo support via config path specification Monorepo/workspaces support via config path specification CLI arg May 3, 2024
@raineorshine
Copy link
Owner

This repo is for npm-check-updates. Did you mean to post this to npm-check?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants