-
Notifications
You must be signed in to change notification settings - Fork 190
Open
Description
We have a monorepo with 100+ workspace NPM packages
Structure:
- parent folder (a react project)
- packages
- package A (a react project)
- package B (a react project)
- packages
When I run, npx react-doctor@latest --no-dead-code --no-ami, there are following issues:
- The current folder or my monorepo is not considered a project even though it is.
- With 100+ packages, it is difficult to put
react-doctor.config.jsonin every package. So, the root folder'sreact-doctor.config.jsonfrom where we are running the command should also be applied.
(.buildenv) ➜ spark-ui git:(skillssh-nandita1) ✗ npx react-doctor@latest --no-dead-code --no-ami
npm warn Unknown project config "public-hoist-pattern". This will stop working in the next major version of npm.
npm warn Unknown project config "strict-peer-dependencies". This will stop working in the next major version of npm.
npm warn Unknown project config "auto-install-peers". This will stop working in the next major version of npm.
npm warn Unknown project config "hoist". This will stop working in the next major version of npm.
npm warn Unknown project config "lockfile-include-tarball-url". This will stop working in the next major version of npm.
npm warn Unknown project config "resolve-peers-from-workspace-root". This will stop working in the next major version of npm.
react-doctor v0.0.29
? Select projects to scan ›
Instructions:
↑/↓: Highlight option
←/→/[space]: Toggle selection
a: Toggle all
enter/return: Complete answer
◯ @rubrik/agent-rewind - packages/agent-rewind
◯ @rubrik/appflows-libs
◯ @rubrik/archival
◯ @rubrik/aura-singletons
◯ @rubrik/aura-ui
◯ @rubrik/auth
◯ @rubrik/cdm9-upgrade
◯ @rubrik/cloud-dspm
◯ @rubrik/cloud-libs
◯ ↓ @rubrik/cluster-config-protection
....
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels