Npm dependencies not being fully scoped is kind of an npm limitation I suppose? Import maps avoid this property.

The simple approach came as a nice surprise to me too. Other coming modules features are likely a bit harder!

Stripped down packuments seem to be scaling surprisingly well even for these huge numbers of versions. Wonder when it breaks down though.

Yes, it’s one exception for convenience here given we don’t have a well defined mime type for typescript. In a true type stripping future there maybe wouldn’t ever be one as well.

Lexing JavaScript / TypeScript is very much the definition of an interpreter. Unless you don’t want to use an interpreter language…

Since JS modules require application/javascript, we default to processing application/typescript and any .ts or .mts files not served with an otherwise valid JS Mime.

Exactly, and only when Typescript is first encountered. Didn’t do any comparisons yet, that would be a good idea to try other libraries like this one.

See the announcement post for an example of running a TypeScript Vue app with #nobuild.

Other recent features including Wasm modules with source phase imports and multiple import maps are also explained in more detail.

guybedford.com/es-module-sh...

A major new feature of this release is a development convenience - TypeScript type stripping support per the proposed type stripping proposal, fully supporting in-browser transpilation of TypeScript.