Andreas Heissenberger

@cyco130 please have a look at this problem - I tested with node version `20.2.0` and the problem still exists.

> I now know the root cause: Node 20 runs ESM loaders in a separate thread but Vavite's loader relies on a global variable. This will require a substantial rework...

I use [vavite](https://github.com/cyco130/vavite) and since the last [changes in vitejs](https://github.com/vitejs/vite/pull/11780) debugging backend (vise-plugin-ssr, trpc and express) with sourcemaps works with `nodejs` 18-20 without any node loader like a charm.

The Problem with the React App is: 1. build/index.html uses absolut pathes to the javascript file - FIX: build react app with relative PUBLIC_URL 2. `FRONT_BASE_CONTEXT_PATH` will be used by...

@kevinreedy can you share your docker file which simulates the lambda environment - at the moment I use a ec2 instance and this would make it much easier to build...

It would also help if someone can implement the option to add conditions for resolve in bun: https://github.com/oven-sh/bun/issues/1527

I did look at Kotekan but this implementation is using the multiple process architecture. My current implementation needs only one process and supports hot reloading in the dev mode `bun...

Is there a rough timeline for bun support?

what is the timeline for this to be merged into master?

This problem still exists - setting `$GOPATH`fixed the problem. MacOS / zsh / golang installed with `brew install gland` `.zprofile`: ```zsh export GOROOT="$(brew --prefix golang)/libexec" export GOPATH="${HOME}/go" export PATH="$PATH:$GOPATH/bin" ```