You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One quick workaround offered by the developer behind jspm is to add registry: npm in the package.json of each github repo used as a dependency in telehash-js's package.json.
The more ideal solution in my opinion is simply to use the github repos' respective npm packages as dependencies instead. I did a quick check on npm and it looks like all of them exist as npm packages already, albeit some of them are a bit out-of-date.
Any thoughts? If the former solution is preferred, I can open some pull requests to make the necessary modifications to the github repos' package.json.
Thanks,
Lewis.
The text was updated successfully, but these errors were encountered:
Ahh, yes, those dependencies are just temporary for testing/dev ease and all need to be published. I'll get them updated hopefully tomorrow, good reminder, thx!
I'm using jspm to manage my front-end dependencies as es6 modules and would like to be able to install telehash-js using using it as well.
However, right now telehash-js has github repositories as dependencies in its package.json, which throws off the jspm installer a bit.
One quick workaround offered by the developer behind jspm is to add registry: npm in the package.json of each github repo used as a dependency in telehash-js's package.json.
The more ideal solution in my opinion is simply to use the github repos' respective npm packages as dependencies instead. I did a quick check on npm and it looks like all of them exist as npm packages already, albeit some of them are a bit out-of-date.
Any thoughts? If the former solution is preferred, I can open some pull requests to make the necessary modifications to the github repos' package.json.
Thanks,
Lewis.
—
Reply to this email directly or view it on GitHub.
Hi,
I'm using jspm to manage my front-end dependencies as es6 modules and would like to be able to install telehash-js using using it as well.
However, right now telehash-js has github repositories as dependencies in its package.json, which throws off the jspm installer a bit.
One quick workaround offered by the developer behind jspm is to add
registry: npm
in the package.json of each github repo used as a dependency in telehash-js's package.json.The more ideal solution in my opinion is simply to use the github repos' respective npm packages as dependencies instead. I did a quick check on npm and it looks like all of them exist as npm packages already, albeit some of them are a bit out-of-date.
Any thoughts? If the former solution is preferred, I can open some pull requests to make the necessary modifications to the github repos' package.json.
Thanks,
Lewis.
The text was updated successfully, but these errors were encountered: