I've spent quite a while trying to track down how exactly vite compiles code. I haven't seen this level of spaghetti code in like 10 years.
There's a CLI that invokes an HTTP server that invokes a plugin system that wraps the plugins' async methods (in these weird callbacks that devtools can't step through btw) that invokes the oxc compiler that, according to the code comments, eventually invokes esbuild but I've not gotten that far. Apparently the next layer in this async stack from hell is rolldown, for whatever reason.
I honestly think this will be a one line fix. I compile other parts of this codebase with esbuild directly and it does transform the accessor keywords. You are most likely just missing a config option buried somewhere in this codebase.
But seriously you shouldn't string together async APIs this way.

Top comments (0)