Anthony Fu
Anthony Fu
Before they made the release, I made a fork with the latest commit to workaround this: https://github.com/antfu/eslint-plugin-import-x/tree/fork#readme
Thanks a lot for the release!
I am looking forward to that! Good idea!
You can write a twoslash implementation following the protocol and reuse `@shikijis/twoslash` package: https://github.com/twoslashes/twoslash/tree/main/packages/twoslash-protocol For example, here is an implementation for ESLint: https://github.com/twoslashes/twoslash/tree/main/packages/twoslash-eslint I don't have the bandwidth to work...
I don't know the context enough, but I have been told to avoid using `export =` as it's not standard ESM syntax and might introduce weird behavior between CJS /...
I found that when you enable `esModuleInterop` on the user side, it seems to generate the correct files. I wonder what's your usage that requires running through `tsc` with the...
> I believe that explicitly setting type: "commonjs" Do you mean by doing it in the package.json? It doesn't seems to solve it from my local reproduction
Based on your TS Playground repo, I made created one as a project: https://github.com/antfu/repro-eslint-stylistic-481 So for I see `esModuleInterop: true` would be the easiest approach
As this plugin is moved to ESM-only, I consider the runtime/type inconsistency is resolved. Thanks for bringing this up
Can you provide a [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example)? Thanks. > [Why reproduction is required](https://antfu.me/posts/why-reproductions-are-required)