Closed LubosK closed 1 year ago
same issue
This is not something react-select
can fix itself, this is reliant on either https://github.com/emotion-js/emotion/issues/3024 and/or https://github.com/kentcdodds/babel-plugin-macros/pull/193 getting fixed/merged.
for those who cannot wait until this issue will be fixed, as temporary! solution you can force to use yaml version "2.2.2" if you define in package.json
in resolutions
part the version you need to use.
e.g.
"resolutions": { "yaml": "2.2.2" },
But be careful and check it twice to ensure it doesn't cause you any other issues
Also worth noting that some on babel-plugin-macros
are of the opinion that this the security vulnerability does not affect the users of babel-plugin-macros. For most I imagine this doesn't matter, but there's likely no real security vulnerability here.
This should be resolved now (https://github.com/kentcdodds/babel-plugin-macros/issues/192#issuecomment-1527703093).
I just install a new fresh next.js app and only your latest version of react-select specifically "5.7.2".
When I run
yarn audit
I got following error.