Skip to content
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.

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

Add warning to next 14.2.x when turbo is enabled #68066

Closed
wants to merge 1 commit into from

Conversation

arlyon
Copy link
Contributor

@arlyon arlyon commented Jul 23, 2024

What?

We are getting numerous reports of people struggling with turbo issues when on 14.2.x branch. We know this is not expected to work, but there is nothing to warn users.

Why?

Better UX for early adopters who want to use turbo in next 14, but who may not know about the existence of the 15 rc branch.

How?

A warning on startup that notifies turbo users about the rc.

@ijjk ijjk added create-next-app Related to our CLI tool for quickly starting a new Next.js application. created-by: Turbopack team PRs by the Turbopack team. Documentation Related to Next.js' official documentation. Font (next/font) Related to Next.js Font Optimization. tests type: next labels Jul 23, 2024
@arlyon arlyon changed the base branch from canary to 14-2-1 July 23, 2024 12:39
Copy link

@XoL1507 XoL1507 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how can i merge?

@leerob
Copy link
Member

leerob commented Aug 23, 2024

I believe we can safely close this now with #68901.

@leerob leerob closed this Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
create-next-app Related to our CLI tool for quickly starting a new Next.js application. created-by: Turbopack team PRs by the Turbopack team. Documentation Related to Next.js' official documentation. Font (next/font) Related to Next.js Font Optimization. tests type: next
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants