You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building react-focal fails for latest lts node v16.15.1 (npm v8.11.0) with the following error message:
BUILDING [ 'keyed', 'react-focal' ]
rm -rf yarn.lock dist elm-stuff bower_components node_modules output
npm ci && npm run build-prod
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @grammarly/focal@0.8.5
npm ERR! Found: @types/react@17.0.5
npm ERR! node_modules/@types/react
npm ERR! dev @types/react@"17.0.5" from the root project
npm ERR! @types/react@"*" from @types/react-dom@17.0.4
npm ERR! node_modules/@types/react-dom
npm ERR! dev @types/react-dom@"17.0.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @types/react@">= 16.9.11 < 17.0.0-0" from @grammarly/focal@0.8.5
npm ERR! node_modules/@grammarly/focal
npm ERR! @grammarly/focal@"0.8.5" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @types/react@16.14.28
npm ERR! node_modules/@types/react
npm ERR! peer @types/react@">= 16.9.11 < 17.0.0-0" from @grammarly/focal@0.8.5
npm ERR! node_modules/@grammarly/focal
npm ERR! @grammarly/focal@"0.8.5" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /root/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-06-19T14_28_15_175Z-debug-0.log
It works when switching back to node v16.13.2 (npm v8.1.2) .
How come?
The text was updated successfully, but these errors were encountered:
Building react-focal fails for latest lts node v16.15.1 (npm v8.11.0) with the following error message:
It works when switching back to node v16.13.2 (npm v8.1.2) .
How come?
The text was updated successfully, but these errors were encountered: