-
-
Notifications
You must be signed in to change notification settings - Fork 483
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
Support different domains config at runtime #2602
Comments
Hi all, |
I coded the fix + tests but I'm unable to push my branch to the repository. @rchl do I need any permissions for this? |
Hi @existe-deja, |
Hi All, |
Hello, |
Any update on this? |
You probably need to fork the project, and submit a PR after adding your fix. Can I see your fix anywhere? |
any update or maybe workaround? |
none that I'm aware of.. still waiting for these domains issues to be resolved |
fyi: NUXT_PUBLIC_I18N_BASE_URL not works in runtime too |
Environment
Reproduction
The code
https://stackblitz.com/edit/nuxt-starter-lm7gng
And a minimal Apache configuration
Describe the bug
I'm encountering an issue with the Nuxt i18n module where its behavior differs between the development and production environments, specifically after a single build process.
Development Environment:
.env
file.Production Environment:
After building the project, I observed two different behaviors based on how the application is started:
First Start (
npm run start
):Second Start (
npm run start:2
):In this case, while the
NUXT_PUBLIC_SITE_NAME
variable is correctly recognized at runtime, theNUXT_PUBLIC_I18N_LOCALES_FR_DOMAIN
variable is not, and the application defaults to the default locale.I suspect there might be an issue with how the i18n module handles domain values in production, particularly after the initial build. Any insights or suggestions on resolving this discrepancy would be greatly appreciated.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: