GitHub user mujohiddin created a discussion: fronted npm build bug
### Bug description
######################################################################
# 1 Base lean superset-frontend build image
######################################################################
FROM --platform=${BUILDPLATFORM:-amd64} node:18-bullseye-slim AS superset-node
ARG NPM_BUILD_CMD="build"
RUN apt-get update -qq \
&& apt-get install -yqq --no-install-recommends \
build-essential \
python3 \
zstd \
&& rm -rf /var/lib/apt/lists/*
ENV BUILD_CMD=${NPM_BUILD_CMD}
WORKDIR /app/superset-frontend
COPY superset-frontend/package.json superset-frontend/package-lock.json ./
RUN npm ci
### Screenshots/recordings
Hi, I have a superset project loaded into Docker. I use it by modifying the
frontend part on a regular server and building it. All the changes are coming
out, but when I push the deployed image to Nexus and start K8S, the changes
made for the frontend are not coming out. I don't understand if I'm missing
something or if I need to do something extra when deploying the images via
Nexus Helm.
npm can't even build the Dockerfile itself
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [ ] I have searched Superset docs and Slack and didn't find a solution to my
problem.
- [ ] I have searched the GitHub issue tracker and didn't find a similar bug
report.
- [ ] I have checked Superset's logs for errors and if I found a relevant
Python stacktrace, I included it here as text in the "additional context"
section.
GitHub link: https://github.com/apache/superset/discussions/34623
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
