Avoid boot loop on NestJS + Prisma build #219
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When booting the NestJS + Prisma test setup, the TypeScript code is compiled. Processmon picks up the outcome of the build as a change and triggers the build to restart, getting stuck in a loop.
I'm not sure why this doesn't happen in CI. This behaviour may be tied to the versions of the dependencies used -- I found this while testing it with
prisma@5.14.0
. Nonetheless, having Processmon ignore thedist
folder makes sense.[skip review]