In the future you may also want to consider using package.json import maps, which would then let you restore imports that look like:

import * as foo from "#vs/base/parts/sandbox/common/sandboxTypes"

In the future you may also want to consider using package.json import maps, which would then let you restore imports that look like:

import * as foo from "#vs/base/parts/sandbox/common/sandboxTypes"

I think there was a discussion about this. Wouldn't we want to stay as close as possible to JS standards where imports are relative?

I guess it depends on what you mean by "standard", but import maps are part of Node (https://nodejs.org/api/packages.html#imports) and supported by all bundlers, alternative runtimes. Technically speaking they can be provided in the browser (https://web.dev/blog/import-maps-in-all-modern-browsers) but it's not super great, but I had assumed that you wouldn't actually need to run your raw ESM output in a browser context (in favor of bundling).

(You of course don't have to use import maps, I just know relative imports can sometimes be annoying and what you had before is very similar to import maps!)

We do support running VS Code out of sources (no bundling) in web too.