4 ms·
> Yeah, I was about to, but then I saw the owners of the project agree to some of the things I absolutely want to not touch at all. Can you elaborate on which
by JoshTriplett 11y ago
> Yeah, I was about to, but then I saw the owners of the project agree to some of the things I absolutely want to not touch at all.
Can you elaborate on which specific areas you're trying not to touch? In your previous comment, you mentioned "rewriting what already works" and "malicious packages and copyright infringement"; anything else?
- diggan 11y agoThings that was raised in the ipmjs repository that I don't feel the a package manager should solve > Prevent worm-like vulnerabilities when adding dependencies > npm scripts, the good, the bad, and the dangerous > Namespace all the things! > Needs for frontend and backend package managers are different > Involve the FSF > Have you thought about malicious packages? > Have you thought about copyright infringement? > trademarking 'ipmjs' so we don't get kik'd These are all issues I want to avoid. Also, I don't want to write yet another package manager, I'm trying to extend NPM and still allow the centralized way that we currently use today, but allow a optional offline-first approach. Feel free to continue reading more about what I said in the ipmjs repository here: https://github.com/ipmjs/ipmjs/issues/13 https://github.com/ipmjs/ipmjs/issues/13