fix: Don't create messages declaration file when running next {start,info,telemetry}#1992
Merged
fix: Don't create messages declaration file when running next {start,info,telemetry}#1992
next {start,info,telemetry}#1992Conversation
…,info,telemetry}`
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
amannn
added a commit
that referenced
this pull request
Sep 4, 2025
…upcoming `next@15.5.1` (#2008) Fixes #2006 Related to #1992 Related to vercel/next.js#82654
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using
createMessagesDeclaration, we previously created the declaration for all of these scenarios:next dev(incl. a watcher)next buildnext typegen(new in Next.js 15.5)next startnext infonext telemetry(not for
next lintthough, because it doesn't consultnext.config.js)The last three items in this list don't really require creating a declaration, so as of this PR we no longer do this.
On the other hand, the newly introduced
next typegencomes in really handy to continue creating the declaration.