undefined | Better HN

0 pointsgavinray2y ago0 comments

The sole reason I haven't migrated to NPM to be honest is the lack of a replacement for "yarn run".

I use "yarn run" incredibly frequently, for things like "yarn run nodemon" and "yarn run tsc" or other executable packages that are local dependencies.

0 comments

4 comments · 1 top-level

hoten2y ago· 3 in thread

Have you tried npx? It comes with Node.

There's also npm run, but perhaps I'm missing something about how they differ

gavinrayOP2y ago

npx doesn't run project-installed packages, it uses global downloads

The "npm run" is a command for running defined scripts in your package.json

The equivalent of "npm run" in yarn is just "yarn", for example: "yarn start"/"yarn dev".

What "yarn run" does is allow you to run binaries installed from "dependencies"/"devDependencies".

Say that I run the following:

  yarn install --dev nodemon ts-node typescript

I can then run

  yarn run tsc --init / yarn run nodemon / yarn run ts-node

And it will invoke the local "./node_modules" package binaries.

This is useful when you want to ensure version-locked, per-project binaries.

hoten2y ago

`npx <package>` does run project installed binaries, if they exist (node_modules/.bin/<package>). In that scenario it's equivalent to `yarn <package>`. Otherwise yes it falls back to a global package, and a prompt to install if missing.

addicted2y ago

npx has supported local packages for quite some time at this point.

j / k navigate · click thread line to collapse