-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build issue with library and project #333
Comments
Yes, you have to update your configuration manually. Library feature is still not fully covered |
This comment has been minimized.
This comment has been minimized.
I am reopening the issue. Since it's happening again. I am providing a sample repo for easy to go reproduction: https://github.com/ruslanguns/nestjs-test-repo Comands |
@jmcdo29 provided a work around in a PR ruslanguns/nestjs-test-repo#1 (comment) hope it can help others to find a temporary solution. |
I have the same kind of issue when putting a typescript file in my root dir (ie at the same level than src folder) But at the end, I guess you might want to build your artifacts in separate folders : dist/libs/utils and dist/website. I mean that you will want to replace src by something else. So you might put your folders libs/utils and website under a src folder @kamilmysliwiec : I understand that library is not fully supported, but if you agree I would be happy to submit a PR to update the current tsconfig file with a rootDir (because it's so easy to add a ts file in rootDir, that's what I always do when I read the graphql doc with generate-typings.ts : https://docs.nestjs.com/graphql/quick-start) |
@jedjebari PRs are always welcome! |
This issue is addressed by the lastest changes to the CLI https://trilon.io/blog/announcing-nestjs-monorepos-and-new-commands |
I'm submitting a...
Current behavior
Default nestjs project when you build it creates a simple structure dist in your root folder:
But if you add a library from schematics and in build it have different behaviour
So nodemon does not work properly since it by default look at dist not at dist/src.
Minimal reproduction of the problem with instructions
Environment
The text was updated successfully, but these errors were encountered: