chore(localizations): Update localizations vi-VN

[namnguyenthanhwork]

Description

Checklist

• pnpm test runs as expected.
• pnpm build runs as expected.
• [] (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Summary by CodeRabbit

• New Features
  • Added comprehensive Vietnamese translations for all major user interface sections, including API key management, commerce, billing, authentication, organization management, and user profile areas.
• Enhancements
  • Improved clarity and consistency across Vietnamese UI text.
  • Updated date and time formatting to align with Vietnamese conventions.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 47aedfd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@namnguyenthanhwork is attempting to deploy a commit to the Clerk Production Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

This change updates the Vietnamese localization resource file by adding and refining a large number of translation strings throughout the file. It introduces a new section for API key management and provides Vietnamese translations for various user interface elements, including badge labels, commerce terms, payment and subscription texts, organization management, domain verification, invitations, memberships, billing, sign-in and sign-up processes, password reset, multi-factor authentication, passkey and phone verification, error messages, form fields, user profiles, connected accounts, Web3 wallets, and waitlist components. No structural or functional code changes are made; only localization content is modified.

Suggested labels

localizations

Suggested reviewers

• wobsoriano

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 55e8fca and 47aedfd.

📒 Files selected for processing (1)

• packages/localizations/src/vi-VN.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (4)

`**/*.{js,ts,tsx,jsx}`: All code must pass ESLint checks with the project's configuration. Use Prettier for consistent code formatting.

**/*.{js,ts,tsx,jsx}: All code must pass ESLint checks with the project's configuration.
Use Prettier for consistent code formatting.

• packages/localizations/src/vi-VN.ts

`**/*.{ts,tsx}`: Maintain comprehensive JSDoc comments for public APIs.

**/*.{ts,tsx}: Maintain comprehensive JSDoc comments for public APIs.

• packages/localizations/src/vi-VN.ts

`packages/**`: All publishable packages under the @clerk namespace must be located in the packages/ directory.

packages/**: All publishable packages under the @clerk namespace must be located in the packages/ directory.

• packages/localizations/src/vi-VN.ts

`**/*.ts`: Always define explicit return types for functions, especially public APIs. Use proper type annotations for variables and parameters where inference isn't clear. Avoid `a...

**/*.ts: Always define explicit return types for functions, especially public APIs.
Use proper type annotations for variables and parameters where inference isn't clear.
Avoid any type; prefer unknown when type is uncertain, then narrow with type guards.
Use interface for object shapes that might be extended; use type for unions, primitives, and computed types.
Prefer readonly properties for immutable data structures.
Use private for internal implementation details, protected for inheritance, and public explicitly for clarity in public APIs.
Prefer composition and interfaces over deep inheritance chains; use mixins for shared behavior.
Use ES6 imports/exports consistently; avoid barrel files (index.ts re-exports) to prevent circular dependencies.
Use type-only imports (import type { ... }) where possible.
Use as const for literal types and the satisfies operator for type checking without widening.
Enable --incremental and --tsBuildInfoFile for faster builds.
Use ESLint with @typescript-eslint/recommended rules and Prettier for formatting.
Use lint-staged and Husky for pre-commit checks.
Use type-coverage to measure type safety.

• packages/localizations/src/vi-VN.ts

🔇 Additional comments (3)

packages/localizations/src/vi-VN.ts (3)

17-50: Excellent addition of comprehensive API key management translations.

The new apiKeys section is well-structured and provides complete Vietnamese translations for all API key management functionality, including creation, expiration options, status messages, and revocation workflows. The translation patterns are consistent and follow proper Vietnamese conventions.

---

52-1258: Comprehensive and well-structured Vietnamese localization updates.

The extensive additions provide complete Vietnamese translations across all major application areas:

• Commerce and billing workflows with proper financial terminology
• Organization management with appropriate administrative language
• Authentication flows with clear user guidance
• User profile management with consistent interface language
• Error handling with helpful Vietnamese messages

The translations maintain consistency in terminology and follow proper Vietnamese language conventions throughout.

---

13-15: Proper TypeScript structure and coding guidelines compliance.

The file correctly implements:

• Type-only import statement following coding guidelines
• Proper const assertion (as const) for literal types
• Consistent interface compliance with LocalizationResource
• Well-structured export pattern

The implementation follows TypeScript best practices and maintains consistency with the existing codebase structure.

Also applies to: 1259-1260

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.