Different behavior with and without --turbo flag in next dev command

[masakinihirota]

Link to the code that reproduces this issue

https://github.com/masakinihirota/next_dev_i18n

To Reproduce

Description:

I am experiencing different behaviors when running the next dev command with and without the --turbo flag in my Next.js application.

Problem
The language conversion function in i18n does not work.

Steps to reproduce:

1. Run next dev command without --turbo flag.
2. Cannot convert from English to Japanese.
3. Run next dev --turbo command.
4. I can convert from English to Japanese.

Expected result:

The behavior of the application should be consistent regardless of whether the --turbo flag is used.

Actual result:

The behavior of the application differs when the --turbo flag is used compared to when it is not used.

Additional information:

I am running a DB called Supabase with Back.
This is not related to the problem part, but this code will not work without setting environment variables.

Current vs. Expected behavior

next 14.1.0
The language conversion did not work when running with

ncu -u

• next 14.1.0

• next 14.2.1

When I updated Next.js.
It stopped even starting.

Provide environment information

>  npx --no-install next info

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 28563
  Available CPU cores: 12
Binaries:
  Node: 20.11.1
  npm: N/A
  Yarn: N/A
  pnpm: 8.15.1
Relevant Packages:
  next: 14.2.1 // Latest available version is detected (14.2.1).
  eslint-config-next: 14.2.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

[github-actions]

We cannot easily recreate the issue with the provided information. Please add a minimal reproduction in order for us to be able to help more efficiently.

Why was this issue marked with the please simplify reproduction label?

There was a reproduction provided, but due to its complexity, we cannot easily reproduce the issue.

An ideal minimal reproduction (unless relevant):

• is not part of a monorepo
• does not require secrets to run
• does not reference private registry dependencies
• has as few dependencies as possible
• excludes unrelated pages/routes
• does not require a database/third-party service to run
• only includes the code necessary to reproduce the issue
• is tested against next@canary to make sure your issue has not already been fixed

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

If you cannot create a clean reproduction, another way you can help the maintainers' job is to pinpoint the canary version of next that introduced the issue. Check out our releases, and try to find the first canary release that introduced the issue. This will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of next by running npm install next@<version>.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please simplify reproduction label that receive no meaningful activity (e.g. new comments with a simplified reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Providing a minimal reproduction from the start without asking helps us look into issues much more quickly, as we can easily verify if the reported bug is related to Next.js. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[samcx]

@masakinihirota By the way, this is the error I get when I try to build your project. We recommend not requiring any steps like this when creating a bug report so we can expedite the process for everyone as we go through issues.

[masakinihirota]

Thanks for the advice.

https://github.com/masakinihirota/next_dev_i18n

Edited to work at minimum.

  "dev": "next dev --turbo"

Start the local server.

pnpm run dev

http://localhost:3000
English to Japanese conversion is not working on the top page.

---

Drop the local server once.

Edit.

  "dev": "next dev"

Start the local server.

pnpm run dev

http://localhost:3000
The English to Japanese conversion is working as expected on the top page.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.