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

Turbo and messages imports #898

Open
markomitranic opened this issue Feb 28, 2024 · 1 comment
Open

Turbo and messages imports #898

markomitranic opened this issue Feb 28, 2024 · 1 comment
Labels
bug Something isn't working upstream-issue This issue is caused by an upstream dependency (e.g. Next.js)

Comments

@markomitranic
Copy link

Description

Turbo doesn't seem to work with dynamically importing messages files. Basically it always loads the first file in the folder.

This is not a next-intl issue, but a Turbo issue instead. I am opening this thread with the goal of tracking the corresponding issues in the Turbo repository, and preventatively providing more information on this for future readers.

Update: I have found that finding Turbo issues on this is actually quite hard. @amannn have you seen any?

Mandatory reproduction URL

https://github.com/markomitranic/dynamic-turbo-imports

Reproduction description

Read the repository Readme, it contains steps. In short:

  • npm run dev - will show different languages on different locales
  • npm run turbo - will show the contents of /messages/_notUsed.json which is not referenced to anywhere in the code.
Screenshot 2024-02-28 at 09 26 34 Screenshot 2024-02-28 at 09 30 56

Expected behaviour

Should show different, and appropriate languages when using turbo.

@markomitranic markomitranic added bug Something isn't working unconfirmed Needs triage. labels Feb 28, 2024
@amannn
Copy link
Owner

amannn commented Feb 28, 2024

Yep, I ran into this too: #718 (comment), see also: vercel/next.js#56531.

It seems like there's some progress being made in this area, so hopefully this gets resolved soon.

We can leave this open for now until the bug is resolved upstream!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream-issue This issue is caused by an upstream dependency (e.g. Next.js)
Projects
None yet
Development

No branches or pull requests

2 participants