Switch from PNPM to Bun, incl. dropping Jest & esbuild

[vorburger]

Changing this (see diff on Files changed tab) breaks the UI - see the web/README.md for how to reproduce:

script.js:19 Uncaught ReferenceError: exports is not defined
    at script.js:19:23

due to the TSC generated web-out/script.js containing this - whatever this means:

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

@edewit you might have a clue about how to fix this? (If you even agree that "type": "module" is recommended? I read it is.)

[vorburger]

Oh, even with my still too limited understanding of the Web ecosystem, I gather it's due to "module": "commonjs" in web/tsconfig.json... but changing that to e.g. this:

 "module": "Node16",
 "moduleResolution": "node16",

then causes pnpm test && pnpm run tsc && pnpm run build (see web/README.md) to STILL fail with:

> [email protected] test /home/vorburger/git/github.com/enola-dev/enola/web
> jest

Error: Jest: Failed to parse the TypeScript config file /home/vorburger/git/github.com/enola-dev/enola/web/jest.config.ts
  TSError: ⨯ Unable to compile TypeScript:
error TS5110: Option 'module' must be set to 'Node16' when option 'moduleResolution' is set to 'Node16'.

    at readConfigFileAndSetRootDir (/home/vorburger/git/github.com/enola-dev/enola/web/node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_/node_modules/jest-config/build/readConfigFileAndSetRootDir.js:116:13)
    at async readInitialOptions (/home/vorburger/git/github.com/enola-dev/enola/web/node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_/node_modules/jest-config/build/index.js:403:13)
    at async readConfig (/home/vorburger/git/github.com/enola-dev/enola/web/node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_/node_modules/jest-config/build/index.js:147:48)
    at async readConfigs (/home/vorburger/git/github.com/enola-dev/enola/web/node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_/node_modules/jest-config/build/index.js:424:26)
    at async runCLI (/home/vorburger/git/github.com/enola-dev/enola/web/node_modules/.pnpm/@[email protected][email protected]_@[email protected][email protected]_/node_modules/@jest/core/build/cli/index.js:151:59)
    at async Object.run (/home/vorburger/git/github.com/enola-dev/enola/web/node_modules/.pnpm/[email protected]_@[email protected][email protected]_@[email protected][email protected]_/node_modules/jest-cli/build/run.js:130:37)
 ELIFECYCLE  Test failed. See above for more details.

How does one do this right?!

PS: This is from & for #1019 ...

[edewit]

node is not the right target as you want to target the web, try and change it to "target": "ESNext",

[vorburger]

@edewit FYI I've just switched from https://pnpm.io to going all-in on https://bun.sh ... this SO much simpler!

Enough already with pulling my hairs because CommonJS vs ES Modules (ESM), TS vs JS, separate bundlers and test frameworks.

Bun "just works" - it's very cool. https://deno.com actually looks even better at least for backend, but less as frontend "runner" (like here).