-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typescript@beta moduleResolution nodenext strategy breaks @emotion #2742
Comments
Thanks for the report, I can confirm this is an issue. Minimal repro: https://github.com/srmagura/emotion-nodenext-repro |
So the way to fix this would be to add the appropriate |
thank you guys! I will review preconstruct#435 |
Testing |
Thank you for reporting back about this 🎉 |
Unfortunately it didn't work because of ESM challenges, but tried changing the `jsx` flag to use `react-jsx` instead. https://www.typescriptlang.org/tsconfig#verbatimModuleSyntax (Tried to upgrade from `importsNotUsedAsValues`, but things are still broken in regards to import elision) https://www.typescriptlang.org/tsconfig#jsx microsoft/TypeScript#47804 emotion-js/emotion#2742 https://www.typescriptlang.org/tsconfig#paths (Also tried setting `jsxImportSource`, but that breaks in ESM because of the forced module resolution path `_ident_/jsx-runtime` :{ )
Current behavior:
Expected behavior:
Environment information:
react
version:18.1@emotion/react
version:18.1** tsconfig **
The text was updated successfully, but these errors were encountered: