Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 2
    After considering the other answers, and exploring messing with my ~/.profile file to ensure I can call the packages in the local node_modules, I've concluded the scripts area of package.json is the best option. You won't need to tell your co-workers to change their profiles or make alias, your scripts will just work.
    – Jared Egan
    Commented Jul 5, 2016 at 15:25
  • I'm using Yarn (work requirement) and most fixes I've seen for this issue use npx. The "./node_modules/.bin is not in $PATH" fixed it for me. Thanks! Commented Apr 22, 2021 at 17:43
  • If you're running in docker, then after npm install, the files might not end up in the node_modules (known linux weirdness, UID/GID??). Then, ofc, the binaries aren't found in node_modules/bin.
    – JWCS
    Commented May 1, 2023 at 22:25