Open davazp opened 5 years ago
Hi, I'm having the same issues. Node version 12.10.0.
I have to use yarn because electron-packager doesn't play nice with pnpm dependencies
just to add, I am working on a fix in a fork of a dependency of electron-packager, https://github.com/MichaelBelousov/flora-colossus/tree/work-with-pnpm, with the goal to upstream it. It would begin the work to let pnpm be used by electron-packager, by resolving dependencies correctly.
EDIT: I should make a separate issue for this comment, maybe better in electron-forge's repo #2670. My fork only demonstrates somewhat how to make that particular package work, electron-packager can succeed now, but copied dependencies still are incorrect, because the copy code in electron-packager is not aware of how pnpm should work either
Is this a feature or a bug?
Please describe the actual behavior. When I remove one of dependencies from a
package.json
and runrush update
, the symbolic link undernode_modules
remains when usingyarn
, but it is removed when usingpnpm
ornpm
.If the issue is a bug, how can we reproduce it? Please provide detailed steps and include a GitHub branch if applicable. Your issue will get resolved faster if you can make it easy to investigate.
You can replicate it with the example repository.
Clone my fork:
git clone https://github.com/davazp/rush-example.git
this is just modified to use yarn.Run
rush update
List symbolic links of a package:
Delete the dependency to
my-tooling
fromlibraries/my-controls/package.json
.Re-run
rush update
List symbolic links again as above. The symbolic link is still there.
What is the expected behavior?
rush rush
should remove the symbolic link as it does with the other tools.If this is a bug, please provide the tool version, Node.js version, and OS.
Tool: Yarn
Tool Version: 1.17.0
Node Version: v12.5.0
Is this a LTS version? No
Have you tested on a LTS version? No
OS: Mac OS X.