-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[BUG] npm does not setup child workspace’s bin or use parent’s bin #4591
Comments
I encounter the same issue. as a workaround, i need to:
and I observe that in the second
this is really annoying for us, hope this could be prioritize and fixed soon. |
Ran into this as well. Running the following caused an error. npm ci
npx lerna run build
npx <workspace-name> The solution I found was to add an npm ci
npx lerna run build
npm update <workspace-name>
npx <workspace-name> That seems to work for me, without having to run a full "install" again. |
I believe I'm running into a related issue here. I've got two git repos: Inside of
When I try to install within But when installing |
What I've done was instead
This way, straight after installing modules, my
This way after whole |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
I cannot run unpublished npx package scripts in child workspaces
Expected Behavior
When using npm, whether from:
I expect to find the
node_modules/.bin
folder for mypackage.json
scripts in the child workspaces, not just parent. I expect npm to link the bin folder in my child package.Or, I expect npm to fallback to/include the parent’s bin, so that unpublished npx commands can still be found.
Steps To Reproduce
npm install
npm run port
Other notes:
These script work fine in the parent package.json, as the
node_modules/.bin
folder exists. However, it will crash in all child workspaces by trying to find a published version on npm.Other notes:
Related issues:
Environment
The text was updated successfully, but these errors were encountered: