IMO Package.json is beautiful. Become gold standard for package management. But it looks like deno seriously hates npm, and cooking up solutions like this. If npm had to be replaced they could do go like packagement with direct links to github. Which package.json already supports.
I think the biggest issue with npm these days is the same as Node.js in general... you wind up in a weird effort to mix/use ESM and CJS packages, which winds up being a bit of a convoluted mess. Where Deno/jsr is based in TS/JS source trees with ESM patterns as the primarily supported method, with npm/cjs as a compatibility shim.
Http (with and without import-maps) supports direct links to github as well.
Comments
IMO Package.json is beautiful. Become gold standard for package management. But it looks like deno seriously hates npm, and cooking up solutions like this. If npm had to be replaced they could do go like packagement with direct links to github. Which package.json already supports.
I think the biggest issue with npm these days is the same as Node.js in general... you wind up in a weird effort to mix/use ESM and CJS packages, which winds up being a bit of a convoluted mess. Where Deno/jsr is based in TS/JS source trees with ESM patterns as the primarily supported method, with npm/cjs as a compatibility shim.
Http (with and without import-maps) supports direct links to github as well.