Help diagnose package.json not picked up #205

New Issue

claunia · 2026-01-29T16:33:47Z

claunia commented

2026-01-29 16:33:47 +00:00

Originally created by @MartinKuhne on GitHub (Aug 28, 2018).

I have a VS project on 0.0.9. The file structure is \source\solutiondir\projectdir and the projectdir has both the client and API, as well as a package.json

My goal is to set 'build' properties as per https://github.com/electron-userland/electron-builder
In particular, I need to add a license file to be distributed with the project (using the extraFiles property)

I tried

  "build": {
    "artifactName": "beer.exe",

That wasn't picked up either

I ran procmon and I can see that package.json is being read.

I think I am on the wrong track here. What is the expected behaviour?

Thanks, Martin

Originally created by @MartinKuhne on GitHub (Aug 28, 2018). I have a VS project on 0.0.9. The file structure is \source\solutiondir\projectdir and the projectdir has both the client and API, as well as a package.json My goal is to set 'build' properties as per https://github.com/electron-userland/electron-builder In particular, I need to add a license file to be distributed with the project (using the extraFiles property) I tried ``` "build": { "artifactName": "beer.exe", ``` That wasn't picked up either I ran procmon and I can see that package.json is being read. I think I am on the wrong track here. What is the expected behaviour? Thanks, Martin

claunia referenced this issue

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

Electron.NET throw exception "Cannot find module" #271

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#205