chore: change prisma generate command to use npm exec#1065
Merged
kentcdodds merged 1 commit intoepicweb-dev:mainfrom Dec 10, 2025
Merged
chore: change prisma generate command to use npm exec#1065kentcdodds merged 1 commit intoepicweb-dev:mainfrom
kentcdodds merged 1 commit intoepicweb-dev:mainfrom
Conversation
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This change replaces usages of npx with npm exec inside the Dockerfile to align with modern npm best practices and improve build determinism, security, and predictability.
Motivation
npx may implicitly download and execute the latest version of a CLI at build time, which can introduce breaking changes without warning. This recently surfaced when Prisma released v7 of its CLI, causing unexpected breakage in an existing project.
Using npm exec ensures that only explicitly installed and lockfile-pinned dependencies are executed during the Docker build, reducing the risk of supply-chain surprises and improving reproducibility in CI environments.