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
It is not possible to use NestJS with newer version (alos it works)
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"^8.2.3" from the root project
npm ERR! peer @nestjs/common@"^7.0.0 || ^8.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/config
npm ERR! @nestjs/config@"^1.2.1" from the root project
npm ERR! 3 more (@nestjs/core, @nestjs/platform-express, @nestjs/testing)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @nestjs/common@"^7.6.6" from [email protected]
npm ERR! node_modules/postgraphile-nest
npm ERR! postgraphile-nest@"^1.0.6" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! peer @nestjs/common@"^7.6.6" from [email protected]
npm ERR! node_modules/postgraphile-nest
npm ERR! postgraphile-nest@"^1.0.6" 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 C:\Users\regis\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\regis\AppData\Local\npm-cache\_logs\2022-10-19T09_07_19_528Z-debug-0.log
I have to use npm i --force all the time...
The text was updated successfully, but these errors were encountered:
It is not possible to use NestJS with newer version (alos it works)
I have to use
npm i --force
all the time...The text was updated successfully, but these errors were encountered: