3 ms·
> JSR isn't a replacement for the npm registry; it's a superset of npm. I first read this line to mean that JSR contains every package on NPM, and was just doi
by MatthiasPortzel 3y ago
> JSR isn't a replacement for the npm registry; it's a superset of npm.
I first read this line to mean that JSR contains every package on NPM, and was just doing some post-processing on them. But it does seem to be its own registry. Maybe the intent of the line was to communicate that you can install packages from both?
- kwhinnery 3y agoI think this is mostly right - "superset" in that JSR modules can depend on npm modules, and projects using npm can use the npm registry and JSR together. The bottom line we'd want to communicate is that JSR is additive to npm, and the two can be used at the same time.
- tumetab1 3y agoThe usage of the "superset" expression is very confusing to me and I bet to many others. I would recommend to use other terms such as "Additive" or "Complementary" to describe JSR.
- nerdponx 3y agoThat's not really what "superset" means, so I think you might want to change the wording.
- grodriguez100 3y ago> I think this is mostly right - "superset" in that JSR modules can depend on npm modules This is not what most people would think when a registry is said to be a “superset” of another.
- lakpan 3y agoJSR is almost literally a subset of npm in features. Npm allows publishing of anything, JSR only actual TS/ESM. Whether those modules have dependencies doesn’t expand the set IMHO