You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior:
After installing the package in a completely new project it cannot be run (both ng s and ng build) at all, indeed I receive this error:
I can confirm the issue. Upgrading TS and Preconstruct doesn't resolve this. I also tried exporting EmotionCache using different kinds of exports. Some other imports (like RegisteredStyles) don't suffer this. My current suspicion is that it's a race condition in our declaration emit. It might be that @emotion/css is emitted when @emotion/cache is not ready yet. IIRC Preconstruct stubs every package with redirects to src before doing the declaration emit but maybe it's not bullet-proof.
I can take a deeper look into it later but perhaps @emmatown will have some insights into this in the meantime.
Current behavior:
After installing the package in a completely new project it cannot be run (both
ng s
andng build
) at all, indeed I receive this error:To reproduce:
npm i --save @emotion/css
css
function in any point of the projectHere's a StackBlitz
Expected behavior:
I expect it will compile and run properly
Environment information:
Completely new project, nothing different set at all
Angular
version: 17.1.2 (18.1.0 in StackBlitz)@emotion/react
version: 11.13.3 (current latest)The text was updated successfully, but these errors were encountered: