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
I agree to follow the code of conduct that this project uses.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Problem description
Electron Forge has locked Yarn support to v1, I don't fully understand why, compatibility issues can be solved by yarnrc.yml settings such as nodeLinker: node-modules to use the node_modules folder instead of Plug'n'Play mode. I've used this setting for years when needed and it solves any issues immediately. I do not believe in locking Yarn support when solutions exist to negate its necessity.
Proposed solution
IF and only if the cause was due to PnP, then it is the developers responsibility to research their tool. PnP issues can be avoided by setting nodeLinker to node-modules to store packages as usual, while also still allowing plugins, and cache to stay active.
Alternatives considered
Not understanding the true scope of the cause, and considering I could be wrong in posting this issue, no other alternatives have been considered.
Additional information
No response
The text was updated successfully, but these errors were encountered:
I've used this setting for years when needed and it solves any issues immediately. I do not believe in locking Yarn support when solutions exist to negate its necessity.
I think that makes sense, will make a PR amending this.
Pre-flight checklist
Problem description
Electron Forge has locked Yarn support to v1, I don't fully understand why, compatibility issues can be solved by
yarnrc.yml
settings such asnodeLinker: node-modules
to use thenode_modules
folder instead of Plug'n'Play mode. I've used this setting for years when needed and it solves any issues immediately. I do not believe in locking Yarn support when solutions exist to negate its necessity.Proposed solution
IF and only if the cause was due to PnP, then it is the developers responsibility to research their tool. PnP issues can be avoided by setting
nodeLinker
tonode-modules
to store packages as usual, while also still allowing plugins, and cache to stay active.Alternatives considered
Not understanding the true scope of the cause, and considering I could be wrong in posting this issue, no other alternatives have been considered.
Additional information
No response
The text was updated successfully, but these errors were encountered: