Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

13.2.2 changed build warnings to errors #46626

Closed
1 task done
simPod opened this issue Mar 1, 2023 · 6 comments · Fixed by #46656
Closed
1 task done

13.2.2 changed build warnings to errors #46626

simPod opened this issue Mar 1, 2023 · 6 comments · Fixed by #46656
Labels
bug Issue was opened via the bug report template.

Comments

@simPod
Copy link
Contributor

simPod commented Mar 1, 2023

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
Binaries:
  Node: 19.6.1
  npm: 9.4.0
  Yarn: 4.0.0-rc.39
  pnpm: N/A
Relevant packages:
  next: 13.2.3
  eslint-config-next: 13.2.3
  react: 18.2.0
  react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

next build

To Reproduce

Have warnings as described in this issue #39161

Describe the Bug

13.2.1 had these issues as warn. Since 13.2.2 those are as error so the build fails.

Expected Behavior

Warn but allow to build.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

@simPod simPod added the bug Issue was opened via the bug report template. label Mar 1, 2023
@ijjk
Copy link
Member

ijjk commented Mar 1, 2023

Hi, this should only be the case for the image config warnings, are you seeing this for others as well?

@simPod
Copy link
Contributor Author

simPod commented Mar 1, 2023

Yes

error - Invalid next.config.js options detected: 
error -     The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack).
error -     The root value has an unexpected property, configOrigin, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack).
error -     The root value has an unexpected property, target, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack).
error -     The value at .amp.canonicalBase must be 1 character or more but it was 0 characters.
error -     The value at .assetPrefix must be 1 character or more but it was 0 characters.
error -     The value at .experimental has an unexpected property, transpilePackages, which is not in the list of allowed properties (adjustFontFallbacks, adjustFontFallbacksWithSizeAdjust, allowedRevalidateHeaderKeys, amp, clientRouterFilter, cpus, craCompat, disableOptimizedLoading, disablePostcssPresetEnv, esmExternals, appDir, extensionAlias, externalDir, externalMiddlewareRewritesResolve, fallbackNodePolyfills, fetchCacheKeyPrefix, forceSwcTransforms, fullySpecified, gzipSize, incrementalCacheHandlerPath, isrFlushToDisk, isrMemoryCacheSize, largePageDataBytes, legacyBrowsers, manualClientBasePath, middlewarePrefetch, newNextLinkBehavior, nextScriptWorkers, optimizeCss, optimisticClientCache, outputFileTracingRoot, outputFileTracingExcludes, outputFileTracingIgnores, outputFileTracingIncludes, pageEnv, preCompiledNextServer, proxyTimeout, runtime, serverComponentsExternalPackages, scrollRestoration, sharedPool, sri, swcFileReading, swcMinify, swcPlugins, swcTraceProfiling, urlImports, enableUndici, workerThreads, fontLoaders, webVitalsAttribution, mdxRs, typedRoutes, webpackBuildWorker, turbo, instrumentationHook, turbotrace).
error -     The value at .i18n must be an object but it was null.
error -     The value at .images.loaderFile must be 1 character or more but it was 0 characters.
error -     The value at .reactStrictMode must be a boolean but it was null.

@mrtnzlml
Copy link

mrtnzlml commented Mar 1, 2023

@ijjk Here is a real-world example: adeira/universe#5788 (check the failing CI)

ijjk added a commit that referenced this issue Mar 1, 2023
This ensures our config schema correctly validates with the default
config we provide.

Fixes: #46626

## Bug

- [x] Related issues linked using `fixes #number`
- [x] Integration tests added
- [ ] Errors have a helpful link attached, see
[`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md)
@ijjk
Copy link
Member

ijjk commented Mar 2, 2023

Hi, this should now be updated in v13.2.4-canary.0 of Next.js, please update and give it a try!

@simPod
Copy link
Contributor Author

simPod commented Mar 2, 2023

Works, thanks

@github-actions
Copy link
Contributor

github-actions bot commented Apr 2, 2023

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants