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
The pages/404.tsx page allows to customise the 404 error displayed to the end user. See https://nextjs.org/docs/advanced-features/custom-error-page#404-page But, since it lives in /pages and not /pages/[locale] as do my other Pages, it doesn't benefit from i18n support. I have successfully displayed the 404 page, but it's the same for all languages (no i18n support). I tried to use getStaticPaths,
The Next.js App Router introduced new heuristics around caching and revalidating. To ensure we’re all discussing the intended behavior of how caching is designed to work, I thought it would be helpful to have a discussion going in-depth on how each piece works. This complements the recently published caching documentation. It’s a follow up to an issue where some members of the community were confu
Core Changes Concept: test mode for Playwright and similar integration tools: #52520 Turbopack: fix hiding node_modules warnings in error overlay.: #54022 ci(next-swc): print glibc version when build: #54026 Adjust internal action proxy export: #54004 Documentation Changes Update 05-client-side-rendering.mdx with latest tanstack query version: #54009 Open Graph Image font declaration moved to corr
Core Changes fix(types): allow nonpromise return types for static functions: #24685 Ensure history navigates correctly with dynamic routes + basePath: #25459 Fix external check for non-local next import: #25518 Ensure providing only query on dynamic route works as expected: #25469 Assume a recent react@experimental if reactRoot is set: #25496 Update to latest webpack 5 and webpack-sources: #25558
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く