Why if you change this

{"include": "../certs/*", "outDir": "./dist/certs1"},
{"include": "../certs", "outDir": "./dist/certs2"}

to this

{"include": "../certs/*", "outDir": "./dist/certs1"},
{"include": "../certs/*", "outDir": "./dist/certs2"}

Thanks, this works like expected with the /*. We used this one in nestjs version 9 all the time successfully:

{"include": "../certs", "outDir": "./dist/certs2"}

After upgrade to nestjs 10 we figured out, that the behavior is different. All our certificates where not copied anymore.

But the main issue/confusion persist. Why nestcli produces different outputs depending on the flag watchAssets true / false. It should not have an effect after running nest build.

After upgrade to nestjs 10 we figured out, that the behavior is different. All our certificates where not copied anymore.

I just did this upgrade today and it took a while to also uncover this.

Previously ../someDir/ would add all the files and directories to the appropriate location in the dist, but now the glob requires ../someDir/*, or ../someDir/** if we're adding child folders too.

Was this change in behaviour intentional or documented? I couldn't find anything.

This should be fixed in 10.4.3

Hi @kamilmysliwiec ,

i increased the nest-cli version to 10.4.3 and the issue still persist. The behaviour is still different. You can try it out with the steps to reproduce from my initial post.

Best regards
Andreas

Thanks for the quick feedback @andreasvh-conceto. It seems that these are 2 different bugs and only one of them was solved in the new release.

I just pushed a quick hotfix and published a new version (10.4.4). Let me know if you're still running into this issue.

Hi @kamilmysliwiec ,

thank you very much. It is working now as expected! :)
Thanks for the quick fix.

Best regards :)