Doing mix assets.deploy after integrating LiveSvelte

Did you add node to your docker environment?

Requirements

For Server-Side Rendering (SSR) to work you need node (version 19 or later) installed in your environment.

Make sure you have it installed in production too. You might be using node in the build step, but it might actually not be installed in your production environment.

You can make sure you have node installed by running node --version in your project directory.

source: GitHub - woutdp/live_svelte: Svelte inside Phoenix LiveView with seamless end-to-end reactivity · GitHub

in my dockerfile i have this line:

RUN apt-get update && apt-get install -y nodejs npm

so it should’ve been installed.

I think i should mention that the issue is present when i run mix assets.deploy and also when i try doing docker compose up

Did you check that those files exist inside of the container? You can check it by starting a new container off your image with a bash session to try to ls and debug from there.

Thank you for your reply

I extracted filesystem out of the image and both node and npm were in there, and when i tried executing RUN node --version and RUN npm --version they both returned their versions as expected, i have npm 10 and node 22 installed if that matters.

Here is my whole dockerfile, i haven’t modified anything except installing curl so i can get access to more recent version of node and then installing it.

# Find eligible builder and runner images on Docker Hub. We use Ubuntu/Debian
# instead of Alpine to avoid DNS resolution issues in production.
#
# https://hub.docker.com/r/hexpm/elixir/tags?page=1&name=ubuntu
# https://hub.docker.com/_/ubuntu?tab=tags
#
# This file is based on these images:
#
#   - https://hub.docker.com/r/hexpm/elixir/tags - for the build image
#   - https://hub.docker.com/_/debian?tab=tags&page=1&name=bullseye-20240130-slim - for the release image
#   - https://pkgs.org/ - resource for finding needed packages
#   - Ex: hexpm/elixir:1.16.2-erlang-26.2.2-debian-bullseye-20240130-slim
#
ARG ELIXIR_VERSION=1.16.2
ARG OTP_VERSION=26.2.2
ARG DEBIAN_VERSION=bullseye-20240130-slim

ARG BUILDER_IMAGE="hexpm/elixir:${ELIXIR_VERSION}-erlang-${OTP_VERSION}-debian-${DEBIAN_VERSION}"
ARG RUNNER_IMAGE="debian:${DEBIAN_VERSION}"

FROM ${BUILDER_IMAGE} as builder

# install build dependencies
RUN apt-get update -y && apt-get install -y build-essential git curl \
    && apt-get clean && rm -f /var/lib/apt/lists/*_*

RUN curl -fsSL https://deb.nodesource.com/setup_22.x | bash -

RUN apt-get install -y nodejs

RUN npm --version
RUN node --version
    
# prepare build dir
WORKDIR /app

# install hex + rebar
RUN mix local.hex --force && \
    mix local.rebar --force

# set build ENV
ENV MIX_ENV="prod"

# install mix dependencies
COPY mix.exs mix.lock ./
RUN mix deps.get --only $MIX_ENV
RUN mkdir config

# copy compile-time config files before we compile dependencies
# to ensure any relevant config change will trigger the dependencies
# to be re-compiled.
COPY config/config.exs config/${MIX_ENV}.exs config/
RUN mix deps.compile

COPY priv priv

COPY lib lib

COPY assets assets

# compile assets
RUN mix assets.deploy

# Compile the release
RUN mix compile

# Changes to config/runtime.exs don't require recompiling the code
COPY config/runtime.exs config/

COPY rel rel
RUN mix release

# start a new build stage so that the final image will only contain
# the compiled release and other runtime necessities
FROM ${RUNNER_IMAGE}
RUN apt-get update -y && \
  apt-get install -y libstdc++6 openssl libncurses5 locales ca-certificates \
  && apt-get clean && rm -f /var/lib/apt/lists/*_*


# Set the locale
RUN sed -i '/en_US.UTF-8/s/^# //g' /etc/locale.gen && locale-gen

ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8

WORKDIR "/app"
RUN chown nobody /app

# set runner ENV
ENV MIX_ENV="prod"

# Only copy the final release from the build stage
COPY --from=builder --chown=nobody:root /app/_build/${MIX_ENV}/rel/justrunit ./

USER nobody

# If using an environment that doesn't automatically reap zombie processes, it is
# advised to add an init process such as tini via `apt-get install`
# above and adding an entrypoint. See https://github.com/krallin/tini for details
# ENTRYPOINT ["/tini", "--"]

CMD ["/app/bin/server"]

Besides that nothing have changed and trying to build an image still results in:

** (Mix) The task "node" could not be found
The command '/bin/sh -c mix assets.deploy' returned a non-zero code: 1

For the error above the problem is there’s no task “node”. Update your mix.exs such that it becomes cmd node .... The cmd task can run shell commands.

After that we might need to look at the file build.js, it might be making wrong assumptions about the current working directory and therefore cannot find the other files it seems to reference.

Okay, so LiveSvelte documentation is wrong? It would be kind of weird that a package with over 1k stars on github has a wrong setup guide and no one noticed.

Thanks for help, i will try to change few things here and there in build.js and will post results.

Hmm, the LiveSvelte docs mentions adding RUN npm install to the Dockerfile.

2. Modify the generated Dockerfile to install curl, which is used to install nodejs (version 19 or greater), and also add a step to install our npm dependencies:
...
+ # install all npm packages in assets directory
+ WORKDIR /app/assets
+ RUN npm install

source: Deployment: Deploying on Fly.io | LiveSvelte Readme

That’s correct, i was surprised because because i had to add cmd before node build.js --deploy --prefix assets. I did everything which was said in docs regarding Dockerfile.

You may send a PR to fix the docs. Compare the Windows and Linux/macOS instructions in the README, they are surprisingly different.

Also notice the example project uses the cmd task:
https://github.com/woutdp/live_svelte/blob/master/example_project%2Fmix.exs#L72