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
Looks like package-lock.json is missing, or should we switch to yarn in Dockerfile, as there is yarn.lock file?
package-lock.json
yarn.lock
~/ChatGPT-CodeReview $ docker build -t before . Sending build context to Docker daemon 17.38MB Step 1/8 : FROM node:18-slim 18-slim: Pulling from library/node 9e3ea8720c6d: Pull complete 22cee24855b2: Pull complete 1f1858138a90: Pull complete 6e736ef1cbb5: Pull complete c4ef7605ff4f: Pull complete Digest: sha256:2ff9841de879f1a2d2d8ef83183c2d93435c451a36d6cfb37b3331d1386c00f8 Status: Downloaded newer image for node:18-slim ---> 249e97c8a29e Step 2/8 : WORKDIR /usr/src/app ---> Running in eb421e4594e0 Removing intermediate container eb421e4594e0 ---> d958cab7c813 Step 3/8 : COPY package.json package-lock.json ./ COPY failed: file not found in build context or excluded by .dockerignore: stat package-lock.json: file does not exist
The text was updated successfully, but these errors were encountered:
Use yarn instead of npm in Dockerfile, fix anc95#80
74f4a79
Use yarn instead of npm in Dockerfile, fix #80 (#81)
3140308
Successfully merging a pull request may close this issue.
Looks like
package-lock.json
is missing, or should we switch to yarn in Dockerfile, as there isyarn.lock
file?The text was updated successfully, but these errors were encountered: