Skip to content
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

Avoid boot loop on NestJS + Prisma build #219

Merged
merged 1 commit into from
Jul 4, 2024

Conversation

unflxw
Copy link
Contributor

@unflxw unflxw commented Jul 4, 2024

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 the dist folder makes sense.

[skip review]

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 the `dist` folder makes sense.
@unflxw unflxw self-assigned this Jul 4, 2024
@unflxw unflxw added the chore label Jul 4, 2024
@unflxw unflxw merged commit 4114dc6 into main Jul 4, 2024
1 check passed
@unflxw unflxw deleted the processmon-ignore-dist-nestjs-prisma branch July 4, 2024 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant