v11.5.0 breaks the Theme export
See original GitHub issueCurrent behavior:
Version 11.5.0 breaks the Theme export in our library. When using the library in React applications I now get
error TS2339: Property 'color' does not exist on type 'Theme'.
This used to work using v11.4.1 (and still does, if I just downgrade)
To reproduce:
n/a - I don’t think I can show this in a CodeSandbox example 😦
Expected behavior:
TypeScript complies the React app without error
Environment information:
react
version: 17.0.2@emotion/react
version: 11.5.0typescript
version: 4.4.4
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[@types/styled-components] 4.1.0 breaks themes · Issue #30536
Defining own props to styled-component is failing for me as well. This code: import styled from 'styled-components' export const Button ...
Read more >ThemeNectar | Changelogs - Salient
Version 3.0.5. Fixed admin javascript from breaking for non-admin users; Decreased theme zip size to get rid of "Are you sure you want...
Read more >Why am I getting "no exported member" errors when ...
The issue. I am trying to upgrade from Angular V9 to V11 and I'm struggling quite a lot with ...
Read more >Breaking Export function on Divi Theme - WordPress.org
I have been able to confirm that on php8.0, WP-Optimize – Cache, Clean, Compress (Version: 3.2.7) is breaking the ability to export DIVI...
Read more >ngx-echarts - npm
Since v5.0 · If you need ECharts GL support, please install it first: npm install echarts-gl -S # or yarn add echarts-gl ·...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can’t afford the time to set up the repro, even if exact steps are given.
@tpict In my case the problem had been caused by a broken dependency tree. We had
@emotion/react
in the dependencies array of both our lib and the React app. We forgot to update the dependency in the app, too, i.e. installing the updated lib broke the dependency tree.As far as theming is concerned: we just followed the docs at https://emotion.sh/docs/typescript In our lib we re-export the theme using
in the lib’s
index.ts