Unnecessary `@babel/core` peer dependency?
See original GitHub issueCurrent behavior:
@babel/core
is a peerDependency of @emotion/styled
, @emotion/css
and @emotion/react
.
To reproduce:
Install one of the above packages when babel is not used, and your dependency manager will likely issue a warning.
Expected behavior:
Nothing in those packages seems to be actively depending on Babel. When using a Vite/esbuild environment, Babel may not be part of the dependencies.
Environment information:
React 18 RC, latest @emotion/react
.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:10
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Warning: unmet peer dependency @babel/core #373 - GitHub
Hi, first, I want to say thank you for this awesome library. When I upgrade from version 11.0.9 to 13.0.0 I get the...
Read more >UNMET PEER DEPENDENCY babel-core@5.8.38
But I seem to encountered a critical error that prevents me from installation. I typed in the following command: npm install --save-dev babel-core...
Read more >Upgrade to Babel 7
Most plugins/top level packages now have a peerDependency on @babel/core . Package Renames. babylon is now @babel/parser. You can still use the shorthand ......
Read more >We're nearing the 7.0 Babel release. Here's all the cool stuff ...
The reason why this is even necessary in the first place is because, ... We are introducing a peer dependencies on @babel/core for...
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
Precisely correct, yes. Thanks for looking at.
Hm, just to make sure that I read this correctly - when installing, let’s say,
@emotion/react
we pull in@emotion/babel-plugin
because it’s a regular dependency and it has non-optional peer dependency on@babel/core
and thus we still end up with unmet peer dependency warnings. Is this correct?