[PR #228] Adds new command line parameters to 'electronize build' #1113

New Issue

claunia · 2026-01-29T16:57:29Z

claunia commented

2026-01-29 16:57:29 +00:00

Original Pull Request: https://github.com/ElectronNET/Electron.NET/pull/228

State: closed
Merged: Yes

Fixes #227.

Adds four new command line parameters to electronize build allowing users to specify the output path, and to provide their own package.json and to specify that they want an npm install

/package-json specifies a package.json file the user wishes to use, and sets /install-modules
/install-modules specifies that electronize build should always npm install
/relative-path specifies a relative path to output binaries
/absolute-path specifies an absolute path to output binaries.

Fixes a directory change side effect of the buildReleaseNuGetPackages.cmd script.
Updates the license information in Package.json to match the license included in the code (ISC -> MIT)

The path specifications change the path provided to electron-packager.

The package-json argument overwrites the bundled package.json after laying out the pre-packed files.

I've tested all four commands manually.

I have noticed you have to be very careful to match your custom package.json with the auto deployed package.json. So documentation for these commands should note that. My procedure was to layout the files normally and then edit the package.json setting it aside to provide as an argument.

Update:
After additional work added one more command line parameter.

**Original Pull Request:** https://github.com/ElectronNET/Electron.NET/pull/228 **State:** closed **Merged:** Yes --- Fixes #227. 1. Adds four new command line parameters to `electronize build` allowing users to specify the output path, and to provide their own package.json and to specify that they want an `npm install` - `/package-json` specifies a package.json file the user wishes to use, and sets `/install-modules` - `/install-modules` specifies that `electronize build` should always `npm install` - `/relative-path` specifies a relative path to output binaries - `/absolute-path` specifies an absolute path to output binaries. 2. Fixes a directory change side effect of the `buildReleaseNuGetPackages.cmd` script. 3. Updates the license information in `Package.json` to match the license included in the code (ISC -> MIT) The path specifications change the path provided to `electron-packager`. The `package-json` argument overwrites the bundled package.json after laying out the pre-packed files. I've tested all four commands manually. I have noticed you have to be very careful to match your custom package.json with the auto deployed package.json. So documentation for these commands should note that. My procedure was to layout the files normally and then edit the package.json setting it aside to provide as an argument. Update: After additional work added one more command line parameter.

claunia added the pull-request label 2026-01-29 16:57:29 +00:00

claunia closed this issue

2026-01-29 16:57:30 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#1113