File size impact

Merging feature/context-sync into main will impact 2 files in 2 groups.

Ping @jolyndenning for review on this one as co-maintainer.

I'd prefer changing the default implementation rather than adding an extra for this. Doing so would be a breaking change to SystemJS, but would match browser and nodejs behavior. See related #2504 where changing to sync was discussed. Also see https://nodejs.org/api/esm.html#importmetaresolvespecifier and https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import.meta/resolve, which both now say that resolve returns a string rather than a promise.

I'd be happy to update the core implementation, if there is an appetite for a major version release. @jolyndenning @guybedford is there a 7.x timeline?

I don't know if systemjs will ever have another release. Migrating to native modules is preferred.

@jolyndenning I assumed that there was some openness to a new release since you were flagged for review.

@guybedford there seems to be some impasse on if a major version (or even a minor version) is in the cards?

Approaching this as an Extra would make this optional for adoption, or the alternative PR implements the breaking change.

I do think the type inconsistency makes this potentially mostly source compatible with older Node code? If somebody found that context.resolve returns a promise and adds an await such that they can resolve the value - then the new runtime behavior for that code would continue to be correct, since awaiting a primitive results in the same value.

I think the only odd thing is if somebody asserted on the type of the return value.

Actually no it wouldn't be source compatible since it would no longer be then-able