Open JuanPedroPontVerges opened 1 year ago
For reproduction , you could share a repo with the minimal config that causes the bug
and is there a way to trigger the types generation explicitly via nest-cli?
@anotheri there is not AFAIK. Types are autogenerated when the app is launched once. However there is a pr to introduce a cli for this particular purpose
It is happening often to me (it sadly looks more like nest builder problem than anything other) The easiest is to make your own script for copying other directories
@Setitch Have you come up with a script that does that? If you did, can you please share it?
v11.0.0-beta on version 11.0.0 the runtime build is removed in favor of custom cli so you could build it ahead of run . Check this pr for usage as docs are not completed yet https://github.com/toonvanstrijp/nestjs-i18n/pull/628
Describe the bug
This has been happening for a while now but didnt have time to take care. So everytime i ran nest build, it sometimes build the i18n into the dist folder, and some other, it doesnt build it, so at the time of running up the built proyect, it throws an error that it cant find the i18n folder in dist directory.
Same happens everytime i ran nest start. Sometimes it finds the i18n folder, and when it doesn't find it, i have to save any file in my proyect (so the server reloads), and after doing that, it finds the folder and logs does not throw any error
This is how my folder structure looks like:
This is my nest-cli.json
And this is how im importing the I18nModule in my app Imports
app.module.ts
Reproduction
Dont know how to reproduct the build command
System Info
Used Package Manager
yarn
Validations