Eskild Diderichsen

I concur. A zero config, catch all, highly opinionated formatter for C# like what prettier is for JavaScript/TypeScript would be an absolute game changer! 🚀 I found this repo looking...

I thought that this typescript ```ts import { isFilePath } from "locter"; ``` was turned into ```js const { isFilePath } = require("locter"); ``` if the compile target is **commonjs**...

@evanw would love your input on this. Is some kind of preprocessing supposed to be done on TypeScript files before it's ready for `esbuild`? Reading from https://esbuild.github.io/content-types/#es-module-interop > `import *...

I'm closing this as it doesn't seem to be going anywhere. I must be misunderstanding something. I mean a lot of projects use esbuild and the internet isn't on fire...

I just encountered this issue using `findAndCount` using `[email protected]`. I wanted to sort joined entities by their primary key as they appear to be unsorted by default. ```jsonc // example...

@wing328 I've tracked down the issue to being related to the flattening of components which you implemented in #12175 As described in the issue. Flattening of types that use primitive...

Sorry, I stopped working on this a while ago. Feel free to pick it up

I managed to isolate the issue in a repo. Updated issue with details.

I set all the commonjs flags I could find and now I'm getting this ```json { "errorType": "TypeError", "errorMessage": "The \"path\" argument must be of type string or an instance...

Turns out that the package `locter` (used by `typeorm-extension`) doesn't work when built using `esbuild`. `locter` uses `import.meta.url` which `esbuild` doesn't support. > There are many node-specific features that esbuild...