Image render diff: node .next/standalone/server.js" & next satrt

[hongdeyuan]

Summary

Hello! 👋;
Recently, during visual regression testing, it was found that there are differences between the two startup modes；

build: standalone
start: node .next/standalone/server.js
os: linux/x86
picture format： .png

visual regression testing result：fail

build: standalone
start: next start
os: linux/x86
picture format：.webp

visual regression testing result： success

Additional information

I personally suspect that the minimal server.js does not include dependency content related to image optimization

standalone build result:

images-manifest.json：

from the packaging results, it appears that the configuration for images manifest no work? 🤔

Who can tell me how to make images-manifestion.json work when starting node .next/standalone/server. js?

Example

No response

[icyJoseph]

This is odd, is it possible for you to just copy the images manifest file, into the .next/standalone directory , and test if that fixes it? Since you seem to have it after standalone builds anyway.

[icyJoseph]

Right, it should've been .next/standalone, ugh, not good. Could you try to make a small reproducible repository? Maybe in Stackblitz, just type next.new onto your browser URL. Make sure it can be built first.

[hongdeyuan]

Right, it should've been .next/standalone, ugh, not good. Could you try to make a small reproducible repository? Maybe in Stackblitz, just type next.new onto your browser URL. Make sure it can be built first.

I seem to have found the reason, it only happens during darwin-arm build and then linux-arm start; Perhaps it would be reasonable for me to build and start in a linux-arm environment;

This is odd, Why does next-start not need to be built and started in the same environment to obtain the correct image format 🤔?

Stackblitz: https://stackblitz.com/~/github.com/hongdeyuan/github-msdbki-tmal2x

[icyJoseph]

Aha, so maybe it's a sharp issue?

[hongdeyuan]

Aha, so maybe it's a sharp issue?

Sorry, it's my fault. 😬

I shouldn't have copied M1's node_madulces directly into a Docker container for use：

  TMP_DIR=vt-tmp
  NODE_IMAGE="node-alpine-git:18"
  NODE_ENV=test

    docker run \
        -d \
        --network ${NETWORK} \
        --name ${APP_TEMP_HOST} \
        -v ${TMP_DIR}:/code \
        -w /code \
        -e NODE_ENV=${NODE_ENV} \
        ${NODE_IMAGE} \
        tail -f /dev/null

    # copy all code(include： node_modules)
    docker cp $WORKSPACE/. ${APP_TEMP_HOST}:/code

    docker exec ${APP_TEMP_HOST} /bin/sh -c "rm -rf .next  && yarn build:mocking"

sharp vary in different system environments;

• local(m1: darwin-arm )
  

• docker(linuxmusl-arm)
  

Fix Script：

  TMP_DIR=vt-tmp
  NODE_IMAGE="node-alpine-git:18"
  NODE_ENV=test

    docker run \
        -d \
        --network ${NETWORK} \
        --name ${APP_TEMP_HOST} \
        -v ${TMP_DIR}:/code \
        -w /code \
        -e NODE_ENV=${NODE_ENV} \
        ${NODE_IMAGE} \
        tail -f /dev/null


    docker cp $WORKSPACE/. ${APP_TEMP_HOST}:/code
   
    # fixed: rm -rf node_modules && yarn
    docker exec ${APP_TEMP_HOST} /bin/sh -c "rm -rf node_modules && rm -rf .next && yarn && yarn build:mocking"