v4

[ayushmanchhabra]

v4.x

• get binaries
  • verify checksum (Verify SHA checksum for downloads #593)
  • cache binaries
  • override cache
  • add support for linux arm (Linux ARM support #494)
  • add support for mac arm (MacOS ARM support #546)
• build mode
  • place app code in package.nw
  • platform specific rc config
  • rename macos helpers (Rename MacOS Helpers #966)
  • source code protection (Source code protection #757)
  • update package.json for production usage (Managed manifest #842)
  • native node modules
    • gyp (Node Native Addon (GYP) #758)
    • nan (Node Native Addon (gyp, nan, cmake, ffi) #970)
    • ffi
    • napi
  • code sign binaries (Code Signing #763)
  • compress outDir (Compress outDir to zip, tar, tgz formats #887)
• package mode RFC (Generate Installer Package of NW.js app #611)
  • NSIS Installer (NSIS Installer #885)
  • AppImage Installer (AppImage Installer #886 )
  • DMG Installer (DMG installer #801)
  • Windows Store compatible #898
  • Snap store compatible
  • Mac Store compatible

[sysrage]

delete outDir dir post zip

This one should be optional.

I'm very interested to see what you find with "chmod binaries" and "code sign binaries".

For the chmod issue in my scripts, I ended up requiring builds to be done in Linux to preserve file permissions from the NW.js tarball as well as dependencies. Otherwise, it was going to be a nightmare to determine which files needed permission changes and to get those permission changes inside a tarball generated in Windows.

I really need to implement code signing, to hopefully avoid the Windows Defender popups. Hoping you make good progress here!

Finally, one more suggested change/enhancement is to implement rcedit to modify the Windows NW.js executable (icon and metadata). I suspect something similar is also needed for macOS packages.

P.S. All of these changes sound like a 4.1, not a 5.0. 😉

[ayushmanchhabra]

For the chmod issue in my scripts, I ended up requiring builds to be done in Linux to preserve file permissions from the NW.js tarball as well as dependencies. Otherwise, it was going to be a nightmare to determine which files needed permission changes and to get those permission changes inside a tarball generated in Windows.

In Windows, chmod only changes the write permission. Possible solution is to pass in an octal value which represents that if platform is Windows.

Finally, one more suggested change/enhancement is to implement rcedit to modify the Windows NW.js executable (icon and metadata).

✅

I suspect something similar is also needed for macOS packages.

Yup, it involves updating the Info.plist files. First need a way to build and test run the demo app in CI so one would not need to have a Mac to debug NW.js Mac apps.