🔧 fix(picture-web): switch from adapter-netlify to adapter-node

The Docker build was failing because adapter-netlify outputs to .netlify/
directory but the Dockerfile expected build output in build/ directory.

Switched to adapter-node with explicit `out: 'build'` configuration
which matches the Dockerfile expectations.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Wuesteon 2025-12-17 19:13:29 +01:00
parent 71cbca07d5
commit 05ad5f1ed8
3 changed files with 350 additions and 236 deletions

View file

@ -40,7 +40,7 @@
"devDependencies": {
"@eslint/compat": "^1.4.0",
"@eslint/js": "^9.36.0",
"@sveltejs/adapter-netlify": "^5.2.3",
"@sveltejs/adapter-node": "^5.4.0",
"@sveltejs/kit": "^2.43.2",
"@sveltejs/vite-plugin-svelte": "^6.2.0",
"@tailwindcss/forms": "^0.5.10",

View file

@ -1,12 +1,15 @@
import adapter from '@sveltejs/adapter-netlify';
import adapter from '@sveltejs/adapter-node';
import { vitePreprocess } from '@sveltejs/vite-plugin-svelte';
/** @type {import('@sveltejs/kit').Config} */
const config = {
// Consult https://svelte.dev/docs/kit/integrations
// for more information about preprocessors
preprocess: vitePreprocess(),
kit: { adapter: adapter() },
kit: {
adapter: adapter({
out: 'build',
}),
},
};
export default config;

573
pnpm-lock.yaml generated

File diff suppressed because it is too large Load diff