You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node.js will add support of 'require'ing of sync ESM soon. If the module page shows whether it is sync or not, then CommonJS consumers can see whether it's usable for them or not. I think this alleviates the pain of switching to JSR for existing npm package authors
The text was updated successfully, but these errors were encountered:
I don't know how to easially achieve this. Not only does the module itself need to not have TLA, but also all of it's dependencies (at all versions that match the constraint now, or in the future) also must not have TLA.
This means we can make this determination for a package at one point in time, but it may then get invalidated if one of it's dependencies adds TLA.
Node.js will add support of 'require'ing of sync ESM soon. If the module page shows whether it is sync or not, then CommonJS consumers can see whether it's usable for them or not. I think this alleviates the pain of switching to JSR for existing npm package authors
The text was updated successfully, but these errors were encountered: