Managed manifest

[ayushmanchhabra]

Issue Type

• Bug Report
• Feature Request
• Other

Current/Missing Behaviour

The NW manifest has to be managed by the programmer. A build step or seperate package.json is required which acts as a NW manifest.

Expected/Proposed Behaviour

If options.managedManifest is enabled, it would parse the Node manifest (package.json at the project root and copy all NW.js relevant properties to the NW manifest inside package.nw. User will also have option to edit those properties (to omit a property, set it to undefined).

A common NW.js Web App development setup would be:

.package.json

{
  "name": "demo-app",
  "version": "0.0.0-development",
  "main": "http://localhost:4200",
  "node-remote": "http://localhost:4200",
}

By enabling managedManifest:

package.nw/package.json

{
  "name": "AppName",
  "version": "1.2.3",
  "main": "index.html",
}

Additional Info

• This brings nw-builder one step closer to nwjs-builder-pheonix in terms of feature parity.
• Exact API is TBD but discussions are welcome.
• Blocked by refactor: build mode #951