-
Notifications
You must be signed in to change notification settings - Fork 609
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
[rush] deploy
command no longer copies the node_modules/.bin
#4961
Comments
Yep also running into this with my projects |
@D4N14L - can you investigate? |
This happens in node 20 as well, had to roll back to 5.134.0. |
Not yet, planning on getting to this at some point this week. Been busy the last little bit, apologies... |
github-project-automation
bot
moved this from Needs Investigation
to Closed
in Bug Triage
Oct 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rush deploy
no longer copies/generatesnode_modules/.bin
folderRepro steps
Reproducible repository: https://github.com/koen-dev/rush-deploy-node-modules-bin-issue
What were you trying to accomplish?
I was trying to use
rush deploy
to set up a deployment for a project, which includes scripts for database migration using the Prisma CLI.What action did you perform that ran into trouble?
After running
rush deploy
, I tried executingrushx migrate
in thecommon/deploy/app1
folder.What went wrong?
The command errored out with
'prisma' not found
, indicating that the Prisma CLI wasn't available. I noticed that thecommon/deploy/app1/node_modules
directory no longer contains the.bin
folder, which seems to be the root of the problem. This behavior differs from version5.134.0
, where the.bin
folder was present after deploying.Expected result: Running
rushx migrate
in thecommon/deploy/app1
folder should successfully execute the Prisma migration script.Actual result: Running
rushx migrate
results in an error stating'prisma' not found
due to the missing.bin
folder incommon/deploy/app1/node_modules
.Details
It looks to be introduced in version
5.135.0
and any later version also contains the same issue.Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/rush
globally installed version?rushVersion
from rush.json?useWorkspaces
from pnpm-config.json?node -v
)?The text was updated successfully, but these errors were encountered: