4 ms·
My only pain point, that I solved with a few lines of elisp, was to go to npmjs, to find the repo link for my dependencies. What's in `node_modules` may be comp
by skydhash 9mo ago
My only pain point, that I solved with a few lines of elisp, was to go to npmjs, to find the repo link for my dependencies. What's in `node_modules` may be compiled to an inscrutable blob and it's rare to find good library docs.
- ricardobeat 9mo agoLife-changing: ghub.io/<package> No idea where I found this but I’ve been using for many, many years.
- hdjrudni 9mo agoHow's it life changing though? You have to know the package name already to do that. And if you're sitting on npmjs looking at the package already, then you're one click away from Github. Furthermore... I don't host my packages on Github :-) Don't think that even works for mine.
- ricardobeat 9mo agoWhen you see an unknown package in a package.json, you can go straight to the source - no search or visiting npm.com