mac --dir
If the dependency listed in package.json is a symbolic link, for example, created by yarn link, then that dependency's node_modules is not included in final ASAR, which made target app unable to run. This worked in electron-builder 19.10.0
@wshamim
I have the same problem after running lerna bootstrap or npm link xx.
Consider to use yarn workspaces as workaround.
Yarn workspaces didn't help. Symbolic linked dependency's dependencies can't be found.
Yarn placed the symbolic linked sub-packages' dependencies in the parent project's root directory's node_modules, and I think they should be resolved like regular packages.
I hope it is fixed now.
@develar, this is still a problem for me. Dependencies which were symbolically linked via yarn link do not get packaged.
Most helpful comment
@develar, this is still a problem for me. Dependencies which were symbolically linked via
yarn linkdo not get packaged.