yarn
yarn copied to clipboard
expected hoisted manifest
Do you want to request a feature or report a bug? It's a question about an error
What is the current behavior?
I have inherited a react project at my new job and when doing yarn install I get the following error: error An unexpected error occurred: "expected hoisted manifest for \"@company/project#@material-ui/core#react-dom\"".
There are multiple projects, all set up in a similar way, but there is only one that is throwing that error.
The problem is that I don't know how to interpret that error. I don't know what a hoisted manifest is (and neither does google). Not sure what is going wrong or what is expected here.
Please mention your node.js, yarn and operating system version. node: 10.5.3 - yarn: 1.15.2 - os: windows 10
Ran into this as well.
The only way I resolved this was by deleting the lock file... which isn't ideal.
the same problem.
error An unexpected error occurred: "expected hoisted manifest for "react-popopo#styled-components#@emotion/is-prop-valid"".
I'm getting this after deleting the yarn.lock file. Any other fixes?
Hello, Hopefully this might help.
We faced the same issue recently.
For more context, we use yarn workspace to load some of our shared libraries.
In order to fix that issue, we had to explicitly declare the list of libraries mentioned in the error in the package.json of the dependency.
ex:
expected hoisted manifest for "react-popopo#styled-components#@emotion/is-prop-valid
means
styled-components or @emotion/is-prop-valid
is not explicitly declared in the package.json of react-popopo
Once that was done, yarn install would work.
Run into this issue as well, yarn-deduplicate helped me
Run into this issue as well,
yarn-deduplicatehelped me
this only help if yarn.lock still exists
Still a problem unfortunately. Blocks me from migrating to yarn.
Y'all should migrate to Yarn 3 (it's not hard). Yarn 1 development has stopped and this'll never be fixed.
delete yarn.lock
then runyarn
work for me
Same problem here.
error An unexpected error occurred: "expected hoisted manifest for \"frontend-hermes#react-router-dom#react-router\"".
I used a slightly safer approach. Instead of deleting the yarn.lock, I just removed all the entries of the problematic library from yarn.lock file.