chore(localizations): Expand French localization

[semleti]

Add translations for the undefined keys of the fr-FR localization

Description

Adds missing translations for the fr-FR localization.
Translated the corresponding en-US localizations to french.

Adjusted some translations to better fit the en-US

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: Localizations

Summary by CodeRabbit

• New Features
  • Expanded French (fr-FR) localization across the app.
  • Added translations for API keys, revoke confirmations, badges and plans, checkout and payments, subscriptions, and billing.
  • Localized organization and profile sections, navbar items, and general status messages.
  • Completed MFA, sign-in, and related authentication flows with French strings.
  • Replaced placeholders with polished French phrasing for buttons, hints, and titles; no functional changes.

[changeset-bot]

🦋 Changeset detected

Latest commit: d71ccc5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@clerk/localizations	Patch
@clerk/clerk-js	Patch
@clerk/chrome-extension	Patch
@clerk/clerk-expo	Patch

Not sure what this means? Click here to learn what changesets are.

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

[vercel]

@semleti 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

French localization resource updated: numerous previously undefined keys in fr-FR were filled with French strings (API keys, UI texts, checkout, org/profile, navbar, subscriptions, MFA, sign-in). Only content changes; no structural, logic, or control-flow edits.

Changes

Cohort / File(s)	Summary
French localization content updates packages/localizations/src/fr-FR.ts	Populated many previously undefined keys with French translations across apiKeys, revokeConfirmation, badges/plans, checkout/payment, organization/profile, navbar, subscriptions, MFA, sign-in and related UI strings; minor phrasing/format tweaks; no logic or structural changes.
Changeset entry .changeset/hip-chefs-end.md	Added a changeset noting a patch release for @clerk/localizations and the addition of missing fr-FR translations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

Je frémis, lapin traducteur, aux mots retrouvés,
Des clés et badges en français bien posés.
Hop — factures, profils et boutons chantent claire,
Un saut, un clin d'œil, la locale est fière.
🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "chore(localizations): Expand French localization" directly and clearly relates to the main change described in the pull request. The changeset updates the fr-FR localization file by translating numerous missing keys from en-US into French across multiple sections, which aligns perfectly with the title's statement of "expanding" French localization. The title is concise, uses appropriate conventional commit format (chore scope), and is specific enough that a teammate reviewing history would immediately understand the PR adds or enhances French translation content. The phrasing is clear and avoids vague terminology.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 39ce410 and d71ccc5.

📒 Files selected for processing (2)

• .changeset/hip-chefs-end.md (1 hunks)
• packages/localizations/src/fr-FR.ts (28 hunks)

🧰 Additional context used

📓 Path-based instructions (8)

.changeset/**

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

• .changeset/hip-chefs-end.md

**/*.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Provide meaningful error messages to developers
Include error recovery suggestions where applicable
Log errors appropriately for debugging
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Profile and optimize critical paths
Validate all inputs and sanitize outputs
Implement proper logging with different levels

Files:

• packages/localizations/src/fr-FR.ts

**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

• packages/localizations/src/fr-FR.ts

packages/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

TypeScript is required for all packages

Files:

• packages/localizations/src/fr-FR.ts

packages/**/*.{ts,tsx,d.ts}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Packages should export TypeScript types alongside runtime code

Files:

• packages/localizations/src/fr-FR.ts

**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use proper TypeScript error types

**/*.{ts,tsx}: 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
Use protected for inheritance hierarchies
Use public explicitly for clarity in public APIs
Prefer readonly for properties that shouldn't change after construction
Prefer composition and interfaces over deep inheritance chains
Use mixins for shared behavior across unrelated classes
Implement dependency injection for loose coupling
Let TypeScript infer when types are obvious
Use const assertions for literal types: as const
Use satisfies operator for type checking without widening
Use mapped types for transforming object types
Use conditional types for type-level logic
Leverage template literal types for string manipulation
Use ES6 imports/exports consistently
Use default exports sparingly, prefer named exports
Use type-only imports: import type { ... } from ...
No any types without justification
Proper error handling with typed errors
Consistent use of readonly for immutable data
Proper generic constraints
No unused type parameters
Proper use of utility types instead of manual type construction
Type-only imports where possible
Proper tree-shaking friendly exports
No circular dependencies
Efficient type computations (avoid deep recursion)

Files:

• packages/localizations/src/fr-FR.ts

packages/localizations/**/*

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Localization files must be placed in 'packages/localizations/'.

Files:

• packages/localizations/src/fr-FR.ts

**/*.{js,ts,tsx,jsx}

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Support multiple Clerk environment variables (CLERK_, NEXT_PUBLIC_CLERK_, etc.) for configuration.

Files:

• packages/localizations/src/fr-FR.ts

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: semgrep-cloud-platform/scan
• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (4)

.changeset/hip-chefs-end.md (1)

1-5: LGTM!

The changeset correctly documents this localization update as a patch version bump with an appropriate description.

packages/localizations/src/fr-FR.ts (3)

17-182: Excellent translation work on the API keys and billing sections!

The French translations are comprehensive and well-structured. The date formatting consistently uses the 'fr-FR' locale throughout this section (except for the known issue at line 85 already flagged in the previous review).

---

183-498: Organization and profile translations look great!

The translations for organization management, member invitations, billing sections, and domain verification are comprehensive and maintain consistent French terminology throughout.

---

736-1316: Impressive translation coverage across sign-up, user profiles, and error messages!

The translations for sign-up flows, task organization, comprehensive error messages (including password complexity and zxcvbn suggestions), user profile management, MFA setup, and waitlist functionality are thorough and maintain consistent French terminology. Great work on this extensive localization effort!

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 6f7da3e and 39ce410.

📒 Files selected for processing (1)

• packages/localizations/src/fr-FR.ts (29 hunks)

🧰 Additional context used

📓 Path-based instructions (7)

**/*.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Provide meaningful error messages to developers
Include error recovery suggestions where applicable
Log errors appropriately for debugging
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Profile and optimize critical paths
Validate all inputs and sanitize outputs
Implement proper logging with different levels

Files:

• packages/localizations/src/fr-FR.ts

**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

• packages/localizations/src/fr-FR.ts

packages/**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

TypeScript is required for all packages

Files:

• packages/localizations/src/fr-FR.ts

packages/**/*.{ts,tsx,d.ts}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Packages should export TypeScript types alongside runtime code

Files:

• packages/localizations/src/fr-FR.ts

**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/development.mdc)

Use proper TypeScript error types

**/*.{ts,tsx}: 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
Use protected for inheritance hierarchies
Use public explicitly for clarity in public APIs
Prefer readonly for properties that shouldn't change after construction
Prefer composition and interfaces over deep inheritance chains
Use mixins for shared behavior across unrelated classes
Implement dependency injection for loose coupling
Let TypeScript infer when types are obvious
Use const assertions for literal types: as const
Use satisfies operator for type checking without widening
Use mapped types for transforming object types
Use conditional types for type-level logic
Leverage template literal types for string manipulation
Use ES6 imports/exports consistently
Use default exports sparingly, prefer named exports
Use type-only imports: import type { ... } from ...
No any types without justification
Proper error handling with typed errors
Consistent use of readonly for immutable data
Proper generic constraints
No unused type parameters
Proper use of utility types instead of manual type construction
Type-only imports where possible
Proper tree-shaking friendly exports
No circular dependencies
Efficient type computations (avoid deep recursion)

Files:

• packages/localizations/src/fr-FR.ts

packages/localizations/**/*

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Localization files must be placed in 'packages/localizations/'.

Files:

• packages/localizations/src/fr-FR.ts

**/*.{js,ts,tsx,jsx}

📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)

Support multiple Clerk environment variables (CLERK_, NEXT_PUBLIC_CLERK_, etc.) for configuration.

Files:

• packages/localizations/src/fr-FR.ts

🔇 Additional comments (1)

packages/localizations/src/fr-FR.ts (1)

1-1307: LGTM on translation quality!

The French translations are well-structured and grammatically correct. The terminology is consistent throughout (e.g., "clé de sécurité" for passkey, "abonnement" for subscription), and proper French accents and formatting are used. The placeholder syntax and date formatting are properly maintained.