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
On build, not all the assets configured are copied. #1828
Labels
Comments
Would you like to create a PR for this issue? |
@kamilmysliwiec Done. #1829 |
@kamilmysliwiec do you have an estimation date when this will get merged & released? Because currently we are blocked by this issue. |
Let's track this here #1829 |
@kamilmysliwiec how about this issue? Is it going to be fixed properly? |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current behavior
When you want to copy a big amount of assets on build, not all the files are copied to dist folder.
The problem is because the assets manager kills the process after 1 second. See: https://github.com/nestjs/nest-cli/blob/master/lib/compiler/assets-manager.ts#L26
Minimum reproduction code
https://github.com/nestjs/nest-cli/blob/master/lib/compiler/assets-manager.ts#L26
Steps to reproduce
Try to copy a big amout of files, which would take more than 1 second and run
nest build
.Expected behavior
It should copy all the files provided in the assets.
Package version
9.1.5
NestJS version
No response
Node.js version
No response
In which operating systems have you tested?
Other
Setting a timeout before stopping the watcher will not work. There should be found other ways of doing it.
I see that chokidar have a
ready
event for when it completes the first scan, which could be used in non watching mode.So the fix would be like:
The text was updated successfully, but these errors were encountered: