Closed rojiwon123 closed 4 months ago
it is not @nestia/sdk bug, and i solved it!
before, in tsconfig.json
"paths": {
"@PRISMA": ["./prisma/client"],
"@SRC/*": ["./src/*"],
"@TEST/*": ["./src/test/*"]
},
after, in tsconfig.json
"paths": {
"@PRISMA": ["./prisma/client/index"],
"@SRC/*": ["./src/*"],
"@TEST/*": ["./src/test/*"]
},
Bug Report
When running the
nestia swagger
command, the path to the prisma client module is parsed to the wrong location. I have pointed the path@Prisma
to the locationprisma/client
via the tsconfig > path setting. When running thetsc -p tsconfig.build.json
command, the path is built correctly. However, when running the nestia swagger command, the path to@Prisma
seems to be parsed to the wrong location.In my code, depth is encountered once more.
I've created a project environment to verify this bug.
Summary
Parsing incorrect module paths
test repository
Nestia Version