broken path in build output about nest-cli HOT 4 OPEN

ts-node without swc works fine it's just slow but i get there's not much you can do about an SWC issue

from nest-cli.

I didn't manage to reproduce your issue on my Ubuntu. Try it out:

git clone [email protected]:tigawanna/nestjs_typeorm.git -b minimal-reproduction
cd nestjs_typeorm/
npm install
npm run start:swc

from nest-cli.

works in wsl , looks like a windows issue

Linux output in dtst/posts/post.module,js

const _common = require("@nestjs/common");
const _postsservice = require("./posts.service");
const _postscontroller = require("./posts.controller");
const _colorsmodule = require("../colors/colors.module");

vs
Windows output in dtst/posts/post.module,js

const _common = require("@nestjs/common");
const _postsservice = require("./posts.service");
const _postscontroller = require("./posts.controller");
const _colorsmodule = require("/?/C:/Users/denni/Desktop/code/node/nestjs/minimal/src/colors/colors.module");

manually correcting the path will fix the issue and it only appears when importing external modules (colors into posts)

from nest-cli.

@tigawanna what if you don't use swc? perhaps that's something we cannot fix on our side

from nest-cli.