Skip to content

fix: resolve Next.js 16 and Turbopack compatibility issues#90

Merged
aralroca merged 2 commits intomainfrom
fix-latest-change
Feb 26, 2026
Merged

fix: resolve Next.js 16 and Turbopack compatibility issues#90
aralroca merged 2 commits intomainfrom
fix-latest-change

Conversation

@aralroca
Copy link
Copy Markdown
Owner

No description provided.

.js 16 and Turbopack compatibility issues
- Avoid adding i18n key to Next.js config when using App Router (only Apps
  using Pages Router need it; adding it in App Router triggers an unsupported
  config warning)
- Use relative aliases ('.' and './*') for @next-translate-root in Turbopack
  resolveAlias so that symlinked local packages resolve correctly
- Add explicit 'next-translate' and 'next-translate/*' aliases for Turbopack
  to handle symlinked local packages that Turbopack cannot follow
- Remove any leaked webpack config from the final config when Turbopack is
  enabled, preventing the 'Using Turbopack with a webpack config' error

ci: update Node.js matrix to 20.x and 22.x

- Drop Node.js 16.x and 18.x from the CI matrix; next@16 requires >=20.9.0
- Upgrade actions/checkout and actions/setup-node from v1 to v4
@aralroca aralroca merged commit 87667ae into main Feb 26, 2026
4 checks passed
@aralroca aralroca deleted the fix-latest-change branch February 26, 2026 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant