dotnet electronize build should not npm install #63

New Issue

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

claunia commented

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

Originally created by @yoDon on GitHub (Nov 12, 2017).

Building and Starting are currently much slower than necessary because every build and every start does a bunch of npm install like tasks that take much longer than the actual build.

The install steps should be handled by a restore or install command, so we don't need to wait for them to complete each time we build/start (or alternatively could we have rebuild/restart commands that are lighter-weight than the full build/start commands, if you want to keep the installs in place?)

Originally created by @yoDon on GitHub (Nov 12, 2017). Building and Starting are currently much slower than necessary because every build and every start does a bunch of npm install like tasks that take much longer than the actual build. The install steps should be handled by a restore or install command, so we don't need to wait for them to complete each time we build/start (or alternatively could we have rebuild/restart commands that are lighter-weight than the full build/start commands, if you want to keep the installs in place?)

claunia added the enhancement label 2026-01-29 16:29:37 +00:00

claunia closed this issue

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

claunia commented

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

@robertmuehsig commented on GitHub (Nov 12, 2017):

At least the start is "faster", because if start detects the node_modules folder it doesn't do a npm install, maybe build should to the same. Good feedback - will consider it for the next drop 👍

@robertmuehsig commented on GitHub (Nov 12, 2017): At least the start is "faster", because if start detects the node_modules folder it doesn't do a npm install, maybe build should to the same. Good feedback - will consider it for the next drop 👍

claunia commented

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

@robertmuehsig commented on GitHub (Nov 15, 2017):

Works like the start enhancement - if we detect the node_modules folder, we skip npm install.

Maybe we need a --force command later on to reinstall npm packages if needed.

@robertmuehsig commented on GitHub (Nov 15, 2017): Works like the start enhancement - if we detect the node_modules folder, we skip npm install. Maybe we need a --force command later on to reinstall npm packages if needed.

claunia commented

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

@damikun commented on GitHub (Oct 31, 2022):

Is there a proper way to pass --force ?

Because some of my packages need to run npm install with force without there is npm checks aplyed and --force skip this checks(validation)...

@damikun commented on GitHub (Oct 31, 2022): Is there a proper way to pass `--force` ? Because some of my packages need to run `npm install` with `force` without there is npm checks aplyed and `--force` skip this checks(validation)...

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Electron.NET#63