-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
CI: Static export locale #7409
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
CI: Static export locale #7409
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I didn't get why we need that ? |
lazy consensus from a thread at https://openjs-foundation.slack.com/archives/CVAMEJ4UV/p1735409553256659 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just checked, cause I want to make sure the crowdin build preview in vercel triggers off of the PR, not the push.
The logic uses VERCEL_GIT_COMMIT_REF
which is the branch name, so we should be good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you check any other API routes that also rely on multi-language generation? Like API routes, IDK.
I checked the pages where |
Lighthouse Results
|
Description
With this PR we aim to only export the default language statically instead of statically exporting all pages based on environment variables
Check List
npm run format
to ensure the code follows the style guide.npm run test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.