You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Après passage de 3.20.3 à 3.21.0, les détails des évènements sont en erreur (ils sont bien listés dans le filtre) :
Au niveau des logs du docker, uniquement le warning suivant au démarrage :
yarn run v1.22.19
$ node ./src/services/rewriteBuildedPages.mjs
$ NODE_ENV=production node ./src/server.js
warn - Invalid next.config.js options detected:
- The root value has an unexpected property, sentry, 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).
See more info here: https://nextjs.org/docs/messages/invalid-next-config
> Ready on http://localhost:3000
Warning: For production Image Optimization with Next.js, the optional 'sharp' package is strongly recommended. Run 'yarn add sharp', and Next.js will use it automatically for Image Optimization.
Read more: https://nextjs.org/docs/messages/sharp-missing-in-production
Warning: data for page "/trek/[slug]" (path "/trek/90296-Parcours-du-patrimoine") is 130 kB which exceeds the threshold of 128 kB, this amount of data can reduce performance.
See more info here: https://nextjs.org/docs/messages/large-page-data
The text was updated successfully, but these errors were encountered:
Bonjour,
Après passage de 3.20.3 à 3.21.0, les détails des évènements sont en erreur (ils sont bien listés dans le filtre) :
Au niveau des logs du docker, uniquement le warning suivant au démarrage :
The text was updated successfully, but these errors were encountered: