Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add opt-in npm-on-ipfs support

See original GitHub issue

As per discussions over on https://github.com/ipfs-shipyard/npm-on-ipfs/issues/94 we’d like make it easy for ipfs-desktop users to try out npm-on-ipfs, and co-host modules that they install.

Offer a prompt to install the ipfs-npm command line tools
alias it as npm or yarn

Issue Analytics

State:
Created 4 years ago
Comments:10 (6 by maintainers)

Top GitHub Comments

3reactions

ericronnecommented, May 15, 2019

This might be a good chance to co-opt @fsdiogo’s help system. Each IPFS Experiment could be automatically installed upon release, and the user notified upon app launch, and offered the option to disable it, e.g. …

Settings could be home base for managing these add ons.

2reactions

hacdiascommented, May 10, 2019

@lidel I agree that it is risky changing binaries. For now, we decided just to install npm-on-ipfs package and tell the user to use ipfs-npm instead of regular npm/yarn commands. This needs some more thought because changing the variable PATH is not as easy as it seems since it might depend a lot on the shell the user is using.

On Windows it’s relatively easy and we already do it to add IPFS to the PATH.