Platform: MINGW64_NT-10.0 [Windows 10 Pro 1809]
There is a user experience issue with how “scripts” work and run. You have start and test which work and operate differently than the rest.
In the default package.json created by many tools it creates a start, build and test script. The start and test always seem to work fine, however the build one never does. It gives a warning:
npm WARN build
npm build called with no arguments. Did you mean to
npm run-script build?
Also when I try to add build2 or something it never finds it. when I run “npm build2”. So and having to type "npm run " for some scripts and just “npm <script” for others is annoying.
Why can I run start and test scripts without the run flag and all others require it? I can do npm run start and npm run test so why are those two special. It makes it more complex when in tutorials that have to go back and forth. This inconsistency is very annoying. Can you make it require run for all or make look for scripts for all of them?
The easiest thing to do would be to require RUN for start and test then all scripts work and operate the same. Having some be different than others is bad user experience which is bad for new users.