Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Version 2.2.0 is not compatible with NestJS 7.x
See original GitHub issueThe version 2.2.0 requires npm packages from NestJs version 8.x.
This forces the application developed using NestJS 7.x to use --legacy-peer-deps.
Could the library be updated to support both NestJS 7.x and NestJS 8.x
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Document and warn about NestJs 7 compatible node versions
Please describe. When following the documented nest new project-name , it does not work with Node version 12/13 based on the following issue....
Read more >@nestjs/config - npm
A progressive Node.js framework for building efficient and scalable server-side applications. NPM Version Package License NPM Downloads ...
Read more >npm ERESOLVE unable to resolve dependency tree NestJs ...
To resolve this issue update the "passport" lib version in your package.json: from "passport": "^0.5.2", to "passport": "^0.4.0", ...
Read more >not compatible with your version of node/npm: google-gax ...
1 which I downloaded installed with several system restarts but my node and npm still remain incompatible. Please what can I do? Experience...
Read more >Migrating from 2.x to 3.0 - Socket.IO
In previous versions, an io cookie was sent by default. ... API change. Below are listed the non backward-compatible changes.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed, thanks for catching that @mahpgnaohhnim !!
this change is removed in this commit https://github.com/pragmaticivan/nestjs-otel/commit/28a93109736927e35a0ea5589ad67ce30bf73709#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
so this problem is now in the current version