5 ms·
I 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 b
by kwhinnery 3y ago
I 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.
- nerdponx 3y agoThat's not really what "superset" means, so I think you might want to change the wording.
- 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.
- 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