This is what it's supposed to look like when running npm run dev
But when run from a container use bun run start it looks like this:
The dockerfile looks like this:
FROM node:20.17.0-alpine3.20 AS deps
WORKDIR /app
COPY package.json package-lock.json .npmrc /
RUN npm ci
COPY . .
# RUN npm run check
FROM deps AS test
RUN npm run testci
FROM deps AS build
# ARG NODE_ENV=development
RUN npm run build
FROM oven/bun:1.1.29-alpine AS publish
COPY --from=build /app/build /out/
WORKDIR /out
ENTRYPOINT [ "bun", "run", "start" ]
import adapter from 'svelte-adapter-bun';
/** @type {import('@sveltejs/kit').Config} */
const config = {
compilerOptions: {
runes: true
},
kit: {
// adapter-auto only supports some environments, see https://svelte.dev/docs/kit/adapter-auto for a list.
// If your environment is not supported, or you settled on a specific environment, switch out the adapter.
// See https://svelte.dev/docs/kit/adapters for more information about adapters.
adapter: adapter()
}
};
export default config;
It really looks like something between the dev build and production build
Reproduction
I can't do a reproduction through stackblitz or anything.
But, it simply is just running npm run dev compared to building the container and running it from there.
I've tried switching out the adapter for just the node adapter and get the same result.
So I assume this is something in the vite build process which is causing problems
So, I've just tried just doing npm run preview in the docker image, and that gives the bad output, where as doing npm run preview locally gives the correct output...
Describe the bug
This is what it's supposed to look like when running
npm run dev
But when run from a container use
bun run start
it looks like this:The dockerfile looks like this:
tailwind.config
looks like this:svelte.config.js
looks like this:vite.config.js
looks like this:my
package.json
:It really looks like something between the dev build and production build
Reproduction
I can't do a reproduction through stackblitz or anything.
But, it simply is just running
npm run dev
compared to building the container and running it from there.I've tried switching out the adapter for just the node adapter and get the same result.
So I assume this is something in the
vite build
process which is causing problemsSo, I've just tried just doing
npm run preview
in the docker image, and that gives the bad output, where as doingnpm run preview
locally gives the correct output...Version and System Info