Solucionado (ver solução)
Solucionado
(ver solução)
1
resposta

Problema na criação do app npm error code ERESOLVE

instalei o node js corretamente, a ultima versao LTS, e quando usava o comando dava esse erro, desinstalei, baixei uma versao anterior, e continua dando erro...

D:\Dev\Alura\010_React\alurabooks>npx create-react-app .

Creating a new React app in D:\Dev\Alura\010_React\alurabooks.

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...


added 1324 packages in 54m

268 packages are looking for funding
  run `npm fund` for details

Installing template dependencies using npm...
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: alurabooks@0.1.0
npm error Found: react@19.0.0
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @testing-library/react@13.4.0
npm error node_modules/@testing-library/react
npm error   @testing-library/react@"^13.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\Andre Bimbatti\AppData\Local\npm-cache\_logs\2025-02-04T17_30_45_721Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\Andre Bimbatti\AppData\Local\npm-cache\_logs\2025-02-04T17_30_45_721Z-debug-0.log
`npm install --no-audit --save @testing-library/jest-dom@^5.14.1 @testing-library/react@^13.0.0 @testing-library/user-event@^13.2.1 web-vitals@^2.1.0` failed
1 resposta
solução!

Descobri que o problema era um conflito da versao 18 com a 19. (nao faço ideia do pq que deu isso) Pra resolver fiz os seguintes passos:

npm install @testing-library/react@latest --save

Pra atualizar as bibliotecas que estavam em conflito. E precisei no meu caso especifico, rodar tambem o comando:

npm install web-vitals

apos isso, rodei o comando npm start e rodou normalmente sem erros a aplicação.