We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello, I updated 0.12.2 to 0.12.4 and after it npm install throws an error:
npm install
npm ERR! Found: @lexical/code@0.12.2 npm ERR! node_modules/@lexical/code npm ERR! @lexical/code@"0.12.4" from the root project npm ERR! @lexical/code@"0.12.2" from @lexical/markdown@0.12.2 npm ERR! node_modules/@lexical/markdown npm ERR! @lexical/markdown@"0.12.4" from the root project npm ERR! @lexical/markdown@"0.12.2" from @lexical/react@0.12.2 npm ERR! node_modules/@lexical/react npm ERR! @lexical/react@"0.12.4" from the root project npm ERR! 1 more (@lexical/react) npm ERR! npm ERR! Could not resolve dependency: npm ERR! @lexical/code@"0.12.4" from the root project npm ERR! npm ERR! Conflicting peer dependency: lexical@0.12.4 npm ERR! node_modules/lexical npm ERR! peer lexical@"0.12.4" from @lexical/code@0.12.4 npm ERR! node_modules/@lexical/code npm ERR! @lexical/code@"0.12.4" from the root project
All packages were updated to the same version:
package.json
{ "dependencies": { ... "@lexical/code": "0.12.4", "@lexical/link": "0.12.4", "@lexical/list": "0.12.4", "@lexical/markdown": "0.12.4", "@lexical/react": "0.12.4", "@lexical/rich-text": "0.12.4", "@lexical/selection": "0.12.4", "@lexical/utils": "0.12.4", ... "lexical": "0.12.4", }
works with --force ofc.
--force
Maybe related: #5245
The text was updated successfully, but these errors were encountered:
sorry, fixed with rm -rf node_modules + remove package-lock.json :\
Sorry, something went wrong.
No branches or pull requests
Hello, I updated 0.12.2 to 0.12.4 and after it
npm install
throws an error:All packages were updated to the same version:
package.json
works with
--force
ofc.Maybe related: #5245
The text was updated successfully, but these errors were encountered: