Stop using 'npm run.' #javascript #webdevelopment #nodejs

node --run made npm faster. #whiteboardtheweb

[Im.liam.]

Very pleased that you're popping up on my feed 🐐

[j.r.r.tolkien]

Yeah I remember typing "npm run start" and it took 2 seconds to run I was so mad I ended up destroying my PC in anger.

[SXsoft]

You know what? You do you, npm run just works, the js ecosystem has enough problems to take I to account, 2 seconds extra compile time will not kill me. I'm just going to use the time to take a sip of water or go for a smoke I don't care

[modydz]

Hey man, I am very grateful for the quality of your content. The videos that deep dive into Suspense and RSC were very helpful, I would truly appreciate if you could do a deep dive into React series and how it works under the hood. Thank you!

[ShortFilmVD]

`node --run` is not meant to match the behaviors of `npm run` or of the `run`
commands of other package managers. The Node.js implementation is intentionally
more limited, in order to focus on top performance for the most common use
cases.
Some features of other `run` implementations that are intentionally excluded
are:

* Searching for `package.json` files outside the current folder.
* Prepending the `.bin` or `node_modules/.bin` paths of folders outside the
current folder.
* Running `pre` or `post` scripts in addition to the specified script.
* Defining package manager-specific environment variables.

[Yegorvs]

I love bun, but disappointed a bit cause they decided to remove all alternatives in favor of javascript core as the only available option

[jjaimealeman]

Isn't pnpm a better alternative? 🤔

[otakugamingyt]

Great now I had add those extra hypens

[otakugamingyt]

Couldn't they just cut short to -r

[ukaszrozewicz]

a one second is 1000 ms, and we're talking about savings of less than 400 ms here, lol. After all, a normal person won't even notice the difference ;)