Consider a user setting or a different default other than install

[AddictArts]

Accidentally hitting F9 when it is an npm install is a bummer in a way.

[omeryagmurlu]

+1 this is a needed feature

[AddictArts]

I ended up just changing apm-npm.js line 45 name: pkg.engines && pkg.engines.atom ? 'apm: clean' : 'npm: clean', It used to have install where clean is now. Line 47 as well args: [ 'run', 'clean' ],

[Hativ]

+1

[noseglid]

If we're changing this, we need to know what we should change to. What would a "sane" default be?

[Hativ]

It should be a setting option. Nothing should be defined as default (but if required I would choose "start"). If no default is defined by the user when executing build the target selection should be shown. The benefit here is the ability to define the default target by myself. I want to run the script "build" in 99% of all cases (automatically on save), so that should be my default.

[noseglid]

Making it configurable should be relatively straight forward. This package needs to check it's configuration - if any of the returned targets from npm is equal to the configuration, put that first in the list.

Having it show the select target list if no default has been set needs a change in the build core package and might be a bit more involved. All though worth considering.