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
optional: remove old node_modules and pnpm-lock before running pnpm install
Describe the bug
When trying to use the new install feature with pnpm-workspace the project gets stuck on pnpm install.
I think it gets stuck on the following prompt: "The modules directory at "C:\Projects\test-nuxt-layers\a\node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n)". Because running the "pnpm install" command will not 'answer' with a Y/n, the process gets stuck.
On bigger projects it will ask this prompt for each node_modules which will trigger the "MaxListenersExceededWarning: Possible EventEmmiter memory leak detected" warning. Like I mentioned here
I am not sure if it is a pnpm bug or a c12 bug, but it seems to be breaking only when using install: true and pnpm-workspace.yaml file
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Node: v20.10.0
"nuxt": "^3.9.0",
"vue": "^3.4.3",
"vue-router": "^4.2.5"
Reproduction
Method1:
Method2:
Describe the bug
When trying to use the new install feature with pnpm-workspace the project gets stuck on pnpm install.
I think it gets stuck on the following prompt: "The modules directory at "C:\Projects\test-nuxt-layers\a\node_modules" will be removed and reinstalled from scratch. Proceed? (Y/n)". Because running the "pnpm install" command will not 'answer' with a Y/n, the process gets stuck.
On bigger projects it will ask this prompt for each node_modules which will trigger the "MaxListenersExceededWarning: Possible EventEmmiter memory leak detected" warning. Like I mentioned here
I am not sure if it is a pnpm bug or a c12 bug, but it seems to be breaking only when using
install: true
andpnpm-workspace.yaml
fileAdditional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: