Martin Adámek

> so in v6 we sure have to keep mikro-orm-esm around Removing it as part of v6 would be a BC, so that's out of question anyway.

> Can I disable or change the rule for this file? Which one? We use dynamic imports in the codebase, e.g. [here](https://github.com/mikro-orm/mikro-orm/blob/1aa940bbd2b1eeddfb3d662c740b346e72e4d74b/packages/core/src/utils/Utils.ts#L191).

> Why don't you have this option enabled? Because I want to see if we do something wrong when integrating 3rd party libraries. AFAIK you can end up with issues...

I wonder if it would be better to target v7 here, I've already set up the branch and I am almost there with ESM rewrite using vitest instead of jest.

Why useless? It adds support for other TS support providers, or did I miss something? > if you would agree moving configuration loader and folder-based discovery out of core module....

I started testing out the ESM rewrite (#6403) and the ts-node solution we have now is not working at all, so there is your answer - ts-node is going out...

I surely think it makes sense to let people choose what they want for TS support, SWC sounds like a better default since it works with the legacy decorators and...

Some bugs are simple, some are not - this one was the latter. But #5784 is finally here. It will need more work (and maybe even a bit different approach),...

Well, that's a completely different feature #706.

Should be just about changing those imports, works fine locally after I fixed them. https://github.com/milesj/docusaurus-plugin-typedoc-api/blob/528be41ed6e67d849072e2cc899eb53f2dea7206/packages/plugin/src/components/VersionBanner.tsx#L5 https://github.com/milesj/docusaurus-plugin-typedoc-api/blob/528be41ed6e67d849072e2cc899eb53f2dea7206/packages/plugin/src/components/ApiIndex.tsx#L6 https://github.com/milesj/docusaurus-plugin-typedoc-api/blob/528be41ed6e67d849072e2cc899eb53f2dea7206/packages/plugin/src/components/Markdown.tsx#L7 ```diff -@docusaurus/theme-common/internal +@docusaurus/plugin-content-docs/client ```