Skip to content

fix: Ensure messages declaration continues working in next dev for upcoming next@15.5.1 #2008

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 4, 2025
Merged

fix: Ensure messages declaration continues working in next dev for upcoming next@15.5.1 #2008

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 17 additions & 8 deletions packages/next-intl/src/plugin/createMessagesDeclaration.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,24 @@ function runOnce(fn: () => void) {
export default function createMessagesDeclaration(
messagesPaths: Array<string>
) {
const shouldRun = [
'dev',
'build',
'typegen'
// Note: The 'lint' task doesn't consult the
// Next.js config, so we can't detect it here.
].some((arg) => process.argv.includes(arg));
// Instead of running _only_ in certain cases, it's
// safer to _avoid_ running for certain known cases.
// https://github.com/amannn/next-intl/issues/2006
const shouldBailOut = [
'info',
'start'

if (!shouldRun) {
// Note: These commands don't consult the
// Next.js config, so we can't detect them here.
// - telemetry
// - lint
//
// What remains are:
// - dev
// - build
// - typegen
].some((arg) => process.argv.includes(arg));
if (shouldBailOut) {
return;
}

Expand Down