Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions apps/web/next.config.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,14 @@ const imageRemotePatterns = [
/** @type {import('next').NextConfig} */
const nextConfig = {
transpilePackages: ["@solid-connect/ai-inspector"],
turbopack: {
rules: {
"*.svg": {
loaders: ["@svgr/webpack"],
as: "*.js",
},
},
},
images: {
unoptimized: true,
remotePatterns: imageRemotePatterns,
Expand Down
2 changes: 1 addition & 1 deletion apps/web/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build --webpack",
"build": "next build",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore --webpack in the build script

Switching apps/web to "build": "next build" enables Turbopack by default in Next 16, but this app still defines a custom webpack function in apps/web/next.config.mjs (lines 59-83). In this configuration, next build fails when a webpack config is present, so the standard pnpm --filter @solid-connect/web build path can break in CI/release builds. Keep --webpack until the webpack block is removed/migrated, or explicitly migrate to a Turbopack-only config path.

Useful? React with 👍 / 👎.

"start": "next start",
"lint": "biome check --write .",
"lint:check": "biome check .",
Expand Down
Loading