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
[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
NestJs config module is not compatible with Typescript 4.
When trying to import the ConfigModule, its not available in IDE quick assist. Forcefully trying to import ConfigModule from @nestjs/config gives an error - Cannot find module '@nestjs/config' or its corresponding type declarations
Expected behavior
ConfigModule should be available after installing @nestjs/config
Minimal reproduction of the problem with instructions
Installed typescript and nestjs cli
Initialise a project, and then install @nestjs/config.
Try to import ConfigModule in AppModule, and it throws an error.
I compared with one of my old projects, and rollbacked the Typescript version to 3, after which the error goes away.
What is the motivation / use case for changing the behavior?
Not as per expectations from the documentation.
Environment
Nest version: 7.5.1
For Tooling issues:
- Node version: 14.15.0
- Platform: Mac
Others:
Typescript version: ^4.0.5
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
NestJs config module is not compatible with Typescript 4.
When trying to import the ConfigModule, its not available in IDE quick assist. Forcefully trying to import ConfigModule from @nestjs/config gives an error - Cannot find module '@nestjs/config' or its corresponding type declarations
Expected behavior
ConfigModule should be available after installing @nestjs/config
Minimal reproduction of the problem with instructions
Installed typescript and nestjs cli
Initialise a project, and then install @nestjs/config.
Try to import ConfigModule in AppModule, and it throws an error.
I compared with one of my old projects, and rollbacked the Typescript version to 3, after which the error goes away.
What is the motivation / use case for changing the behavior?
Not as per expectations from the documentation.
Environment
The text was updated successfully, but these errors were encountered: