Skip to content
Discussion options

You must be logged in to vote

nestjs v8 with typescript v5 is a rough combo - thats a pretty big jump. the path alias issues are probably because ts5 handles module resolution differently.

few things to check:

  1. make sure your tsconfig has these settings:
  • moduleResolution should be node (not bundler or nodenext for nest v8)
  • baseUrl and paths need to match your project structure
  1. if youre using ts-node or swc for running, they need path alias support too:

for ts-node add tsconfig-paths:
npm install tsconfig-paths

then in nest-cli.json or package.json scripts:
ts-node -r tsconfig-paths/register src/main.ts

  1. nestjs 8 was designed for ts4.x. jumping to ts5 might cause decorator metadata issues. check if emitDecoratorM…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@ThallesP
Comment options

Answer selected by ThallesP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants