We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
we use a node:12 image on our gitlab-ci. there yarn install should trigger prisma2 generate.
yarn install
prisma2 generate
it thows an error:
Error: Error: Command failed with ENOENT: /path/to/project/node_modules/prisma2/query-engine-debian-openssl-1.1.x --enable_raw_queries cli --dmmf
i can also log into the pod running this build and i see that this path indeed does not exist.
seems similar to #1635 and #1642
the base image is not an alpine, but the node:12 image, so it should be supported.
node:12
The text was updated successfully, but these errors were encountered:
edit: i removed node_modules on that pod and did a yarn install again and now it works.
have to check whether this has to do with how we cache node_modules on gitlab-ci
Sorry, something went wrong.
closing, it seems the cached node_modules folder had not the right binaries.
maybe it would be good if prisma2 generate would try to reinstall missing stuff
@macrozone We further improved our binary checking logic in prisma/prisma-client-js@5519704 so this should not occur anyways now. It is avaliable in alpha
No branches or pull requests
we use a node:12 image on our gitlab-ci. there
yarn install
should triggerprisma2 generate
.it thows an error:
i can also log into the pod running this build and i see that this path indeed does not exist.
seems similar to #1635 and #1642
the base image is not an alpine, but the
node:12
image, so it should be supported.The text was updated successfully, but these errors were encountered: