You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
For now, this can allow next.config.js to understand where it's been run and apply different options. We should probably have better compatibility in the future, which would make this unnecessary for this usecase.
Test Plan: Modified a next.config.js to change its behavior based on the presence of this option. Verified non-turbo case doesn't have this exposed.
The reason will be displayed to describe this comment to others. Learn more.
We need something compile-time evaluatable to shortcircut e. g. if(!process.turbopack) and skip resolving references in that block.
Sadly we are missing the infrastructure for that still. So this will be a bigger task
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.
For now, this can allow
next.config.jsto understand where it's been run and apply different options. We should probably have better compatibility in the future, which would make this unnecessary for this usecase.Test Plan: Modified a
next.config.jsto change its behavior based on the presence of this option. Verified non-turbo case doesn't have this exposed.