Package.json location #293

New Issue

claunia · 2026-01-29T16:35:54Z

claunia commented

2026-01-29 16:35:54 +00:00

Originally created by @rpadevops on GitHub (Mar 27, 2019).

As a developer, I want to be able to modify the package.json in order to set up the metadata for the electron app.

Therefore the question, why did you decide to compile the package.json and other files into the CLI tool? Every time I want to increase the version number or change anything in the package.json, I need to build the Electron.Net project in order to get the adjusted CLI.
Wouldn't it make more sense to add the package.json to the referencing project and use the CLI version only if the file isn't in place?

Originally created by @rpadevops on GitHub (Mar 27, 2019). As a developer, I want to be able to modify the package.json in order to set up the metadata for the electron app. Therefore the question, why did you decide to compile the package.json and other files into the CLI tool? Every time I want to increase the version number or change anything in the package.json, I need to build the Electron.Net project in order to get the adjusted CLI. Wouldn't it make more sense to add the package.json to the referencing project and use the CLI version only if the file isn't in place?

claunia closed this issue

2026-01-29 16:35:54 +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#293