fix(next): Inject SDK in dev mode #6368
Merged
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.
Fixes #6321
In #6206 we switched up our logic not to always include the SDK on
/app
route. This broke the injection mechanism in dev mode where_app
is the only entry point that is always hit. In dev mode, pages defined by the user are not considered entry points so they were skipped by our injection logic.This PR fixes this by always injecting the SDK into
_app
in dev mode. This is probably not optimal because it doesn't really reflect what is happening when a Next.js is built using prod mode but it's as close as we can get with reasonable effort.