Abandoned, as newer npm / yarn doesn't work will with plain copy pasta tarballs.
Has npm link
or yarn link
got you down? 😃😭
Does your linked package have troublesome "singleton" dependencies that begin to double-up, like react
?
Maybe your code bundler trips up when traversing weird ol' symlinks?
Perhaps you're allergic to or straight up don't trust those `link` commands? 🤷
...
👉🦘 Well, give up now and try linkaroo
. 🦘👍😉 wink
npm i -g linkaroo
Paaaaack your package!
$ cd my-pkg && npm run build
$ linkaroo pack
Liiiiiink it up!
$ cd my-app
$ linkaroo link "my-pkg@1.0.0"
Repeat steps 1 & 2 when my-pkg
chaaaaanges.
👏 DONE 👏
👏 DONE 👏
Sponsored* by the Australian Government
*: It's not
Using npm/yarn link
can be dissapointing in real life, because our node & bundlers get messed up traversing symlinks; they get stuck and find interdependant packages they were NOT suppose to... 😡
So let's just pretend to publish
and install
during local iterations.
That's what these two commands pretend to do:
pack
will prepare your package in a tarball (like publishing) and put it somewhere safe on your machinelink
will unpack that tarball into your other dependantsnode_modules/
directory (like a dirty lazynpm install
)
Thanks to the NPM team for making their CLI easy to use.
MIT