fix(vite): sharp als ssr.external markieren
All checks were successful
Build & Publish Docker Image / build-and-push (push) Successful in 2m17s
All checks were successful
Build & Publish Docker Image / build-and-push (push) Successful in 2m17s
Der Server-Bundle-Schritt (Rollup via adapter-node) kann sharp's dynamic-require fuer die native Plattform-.node-Binary nicht aufloesen und bundelt kaputten Code ins Image. ssr.external sorgt dafuer, dass sharp zur Laufzeit regulaer aus node_modules geladen wird, wo der Docker-Build die @img/sharp-linuxmusl-arm64-Binary korrekt abgelegt hat. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -3,6 +3,13 @@ import { defineConfig } from 'vitest/config';
|
|||||||
|
|
||||||
export default defineConfig({
|
export default defineConfig({
|
||||||
plugins: [sveltekit()],
|
plugins: [sveltekit()],
|
||||||
|
// sharp muss extern bleiben: der Server-Bundle-Schritt kann sharp's
|
||||||
|
// dynamic-require fuer die native .node-Binary nicht aufloesen. Wenn
|
||||||
|
// sharp nicht gebundelt wird, laedt Node es zur Laufzeit regulaer aus
|
||||||
|
// node_modules/@img/sharp-linuxmusl-arm64, das dann funktioniert.
|
||||||
|
ssr: {
|
||||||
|
external: ['sharp']
|
||||||
|
},
|
||||||
test: {
|
test: {
|
||||||
include: ['tests/**/*.test.ts'],
|
include: ['tests/**/*.test.ts'],
|
||||||
globals: false,
|
globals: false,
|
||||||
|
|||||||
Reference in New Issue
Block a user