Closed 18steps closed 7 years ago
Thanks mate!;)
Not sure whether I've already solved this once, but I didn't encounter any issue by using the package manager for windows (both x32 and x64).
What I would also suggest (packaging-related) is finding a way to avoid boundling the typescript source code: there is a clean way to create the windows standalone without the "original source code", which is removing all the typescript files and folders from the generated package. I'm currently doing it manually, but I'm pretty sure there is a cleverer way to avoid it using electron-packager.
When people inevitably want to package the electron app, they will have problems if
main.js
is not in the same folder asnode_modules
.Therefore, move
main.js
to root folder, and updatemainWindow.loadURL()
to use the new relative location ofindex.html
.See this issue with electron package manager not bundling node_modules. It was leaving the
node_modules
in the output folder empty, when it should have been bundling the ones used by the application.It's kind of a quiet problem until you create a Windows installer, because the exe in the output folder will run with the
node_modules
from the ancestornode_modules
folder, but there will be nonode_modules
bundled.