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 you add win64 to the nwjsplatforms option of the Gruntfile, it will silently fail without errors when building, and produce a blank nwjs exe.
It would be very helpful if we didn't have two separate, unrelated processes for building Mac and Windows apps. It would mean you don't have to do two different kinds of updating when you want to update nwjs to support modern JavaScript, for example.
The only related issue I could find: This might be because Windows does not allow path names over 256 characters, and we probably have well-nested node_modules directories (somewhere among our 340 installed npm modules!). See discussions on nwutils/nw-builder#107 and nwjs/grunt-nw-builder#118. But I don't think our node modules get packaged with the app? Oh wait I think nwjs automatically looks for a node_modules directory and packages it?
The text was updated successfully, but these errors were encountered:
Or maybe it'd be better to adopt a different, modern nwjs app build process, since grunt-nw-builder doesn't seem to be super actively maintained anymore?
One neat side effect of the NW.js => Electron upgrade from release v1.1.0: the build processes for the Windows and Mac (and Linux) versions of the authoring tool are now one and the same.
When you add
win64
to thenwjs
platforms
option of the Gruntfile, it will silently fail without errors when building, and produce a blank nwjs exe.It would be very helpful if we didn't have two separate, unrelated processes for building Mac and Windows apps. It would mean you don't have to do two different kinds of updating when you want to update nwjs to support modern JavaScript, for example.
The only related issue I could find: This might be because Windows does not allow path names over 256 characters, and we probably have well-nested
node_modules
directories (somewhere among our 340 installed npm modules!). See discussions on nwutils/nw-builder#107 and nwjs/grunt-nw-builder#118. But I don't think our node modules get packaged with the app? Oh wait I think nwjs automatically looks for anode_modules
directory and packages it?The text was updated successfully, but these errors were encountered: