Should also strip the __esModule property? This still got emitted currently:

Object.defineProperty(exports, "__esModule", {
  value: true
});

Also, these JSON imports and external imports weren't resolved as they should? They still emit a .js file instead of .json or inlining the import

Should also strip the __esModule property? This still got emitted currently:

Done

Also, these JSON imports and external imports weren't resolved as they should? They still emit a .js file instead of .json or inlining the import

emitting .json is now also implemented
externals are properly resolved (by ignoring) but not inlined yet

also, export statements aren't transformed.
they are firstly all initialized within a single VariableAssignment to undefined, then get assigned the actual value later.

thats specific to typescript: https://www.typescriptlang.org/play?module=1#code/KYDwDg9gTgLgBAG2PAhnAvHAjAbiA
this PR is mostly about fixing the webpack issues themselves but it could be implemented later

acked

Externals are inlined now:

// 0: module.exports = require("worker_threads");
// 1: var tmp = __webpack_require__(0); ...
// 1 gets changed to:
import { MessageChannel, parentPort, Worker, workerData } from "worker_threads";

And import/export paths are properly resolved again for existing modules:
import * as json from "./1.json"; instead of import * as json from "1";

🤔 is anything still blocking this pr?

yeah there are a couple issues like creating multiple conflicting import { a } from
didn't have much time recently to work on it

👌

yeah there are a couple issues like creating multiple conflicting import { a } from didn't have much time recently to work on it

my few cents: generate names like import { a as a$chunkId$ } from './chunkId.js';