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
When using the bump or publish command my node_modules (of the root workspace) are always cleared since the changes in #942.
When running the same command pnpm install --lockfile-only --ignore-scripts in my terminal if the package versions have been bumped, the node_modules are not removed.
I have checked the codebase of execa (package used to call pnpm) and in the pnpm codebase. But I can't seem to find any reason why it deletes the node_modules when running through beachball and why they are not deleted when running the pnpm command myself.
The text was updated successfully, but these errors were encountered:
If you run pnpm in a subdirectory, does that clear the root node_modules? I'm wondering if the issue is that beachball is running pnpm in the wrong directory.
No it doesn't clear the node_modules then either. It's a weird bug. I don't even know if it's a beachball or pnpm issue or maybe a combination where beachball enables a certain config or option in pnpm forcing the "recreation" of the node_modules
When using the bump or publish command my node_modules (of the root workspace) are always cleared since the changes in #942.
When running the same command
pnpm install --lockfile-only --ignore-scripts
in my terminal if the package versions have been bumped, the node_modules are not removed.I have checked the codebase of execa (package used to call pnpm) and in the pnpm codebase. But I can't seem to find any reason why it deletes the node_modules when running through beachball and why they are not deleted when running the pnpm command myself.
The text was updated successfully, but these errors were encountered: