fix(build): suppress circular-chunk warning (server-only, no runtime impact)
CI / check (push) Successful in 32s
CI / tests-imaging-browsers (push) Successful in 1m53s
CI / tests-integration (push) Successful in 2m4s
CI / tests-unit (push) Successful in 2m47s
CI / tests-quality (push) Successful in 1m12s
CI / tests-ui (push) Successful in 5m49s
CI / preflight (push) Skipped
CI / deploy (push) Successful in 3m29s
CI / check (push) Successful in 32s
CI / tests-imaging-browsers (push) Successful in 1m53s
CI / tests-integration (push) Successful in 2m4s
CI / tests-unit (push) Successful in 2m47s
CI / tests-quality (push) Successful in 1m12s
CI / tests-ui (push) Successful in 5m49s
CI / preflight (push) Skipped
CI / deploy (push) Successful in 3m29s
This commit is contained in:
1 parent
ef0c425598
commit
095353012a
1 file changed
+15
@@ -167,6 +167,21 @@ const nextConfig: NextConfig = {
|
||||
formats: ["image/avif", "image/webp"],
|
||||
},
|
||||
|
||||
// The SWF/Nitro image pipeline (src/lib/services/swf, src/lib/services/image-*)
|
||||
// pulls shared helpers into several server chunks that webpack reports as a
|
||||
// circular dependency between chunks with runtime. The cycle only affects
|
||||
// server-side module caching of already-loaded chunks and has no runtime
|
||||
// impact, so suppress the noisy warning instead of refactoring the shared
|
||||
// helpers (which would risk the hot image path). Revisit if a real deadlock
|
||||
// appears.
|
||||
webpack(config) {
|
||||
config.ignoreWarnings = [
|
||||
...(config.ignoreWarnings ?? []),
|
||||
/Circular dependency between chunks with runtime/,
|
||||
];
|
||||
return config;
|
||||
},
|
||||
|
||||
async headers() {
|
||||
return [
|
||||
{
|
||||
|
||||
Reference in new issue
Block a user