Skip to content

Commit

Permalink
Merge pull request #601 from Hexastack/fix/patch-lock-file-issue
Browse files Browse the repository at this point in the history
fix: patch-lock-file error in dev & prod mode
  • Loading branch information
marrouchi authored Jan 22, 2025
2 parents 2d05357 + 52e3ce9 commit 49e812b
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions frontend/Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,9 @@ COPY ./widget ./widget

RUN npm install


# used to by pass Next.js paching lock file
ENV NEXT_IGNORE_INCORRECT_LOCKFILE=true
ENV NODE_ENV=development
ENV CHOKIDAR_USEPOLLING=true
ENV WATCHPACK_POLLING=true
Expand All @@ -64,6 +67,8 @@ CMD ["npm", "run", "dev", "--", "-p", "8080"]
FROM base AS production
WORKDIR /app

# used to by pass Next.js paching lock file
ENV NEXT_IGNORE_INCORRECT_LOCKFILE=true
ENV NODE_ENV=production
# Uncomment the following line in case you want to disable telemetry during runtime.
ENV NEXT_TELEMETRY_DISABLED 1

Check warning on line 74 in frontend/Dockerfile

View workflow job for this annotation

GitHub Actions / build-and-push

Legacy key/value format with whitespace separator should not be used

LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Expand Down

0 comments on commit 49e812b

Please sign in to comment.