4 ms·
Why not GX? https://github.com/whyrusleeping/gx https://github.com/whyrusleeping/gx (It's a language-agnostic packaging tool built around IPFS)
by okket 11y ago
Why not GX? https://github.com/whyrusleeping/gx https://github.com/whyrusleeping/gx
(It's a language-agnostic packaging tool built around IPFS)
- diggan 11y agoTo not reinvent the whole package mananger. We're trying to reuse the existing NPM CLI for things and only change where the packages comes from. Having something that works with both existing package.json dependencies and an extra field in the package.json, is the goal. People should be able to use IPFS when it's available, and fall back to NPM central registry when needed.
- nawitus 11y agoDoes gx support multiple, parallel versions of the same dependency (e.g. a dependency tree)? How does it work, and does it work with Node.js's require/resolve algorithm?
- whyrusleeping 11y agoauthor of gx here, gx packages are referenced unambiguously by the hash of their contents. You can have multiple versions of the same package without even having to think about it :)
- fiatjaf 11y agoWhy can't GX and this tool store packages in the same format, so one can use packages from the other?