chore: add next-intl configuration #36
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
Codex Review: Here are some suggestions.
Reply with @codex fix comments to fix any unresolved comments.
About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".
| images: { unoptimized: true }, // 避免使用 Next Image 优化服务 | ||
| }; | ||
|
|
||
| export default withMDX(config); | ||
| export default withNextIntl(withMDX(config)); |
There was a problem hiding this comment.
[P1] Enable next-intl plugin without locale-aware routes
Wrapping the Next.js config with createNextIntlPlugin('./i18n.ts') configures the app to rewrite requests to locale-prefixed paths (e.g. /en, /zh). The current app directory only contains root-level routes (app/page.tsx, app/docs/...) and does not provide a [locale] segment or locale-aware layouts. After this change, users will be redirected to locale-prefixed URLs that have no matching pages, leading to 404s for every request. The locale directory structure and layouts need to be added before enabling the plugin.
Useful? React with 👍 / 👎.
longsizhuo
deleted the
codex/set-up-internationalization-with-next-intl
branch
Summary
i18n.tswith supported localesnext-intlnext-intldependencyTesting
pnpm build(fails: stuck while exporting pages)https://chatgpt.com/codex/tasks/task_e_68c7012be00083238ad1872e3655e9cc