Skip to content

refactor: use WXT i18n - #7

Merged
jevin98 merged 1 commit into
mainfrom
codex/wxt-i18n
May 14, 2026
Merged

refactor: use WXT i18n#7
jevin98 merged 1 commit into
mainfrom
codex/wxt-i18n

Conversation

@jevin98

Copy link
Copy Markdown
Owner

Summary

  • Replace the Vue i18n dependency with WXT/browser native i18n via browser.i18n.getMessage.
  • Move existing English and Chinese translations into public/_locales/*/messages.json.
  • Localize extension manifest name and description with __MSG_*__ keys.

Why

WXT already supports browser extension i18n through _locales and the extension i18n API, so the extra vue-i18n dependency is no longer needed.

Impact

  • Translation now follows the browser/extension locale instead of an in-panel manual language selector.
  • Removes vue-i18n and related lockfile entries while keeping the latest main dependency versions.

Validation

  • pnpm install --frozen-lockfile
  • pnpm run compile
  • pnpm run build:chrome
  • Searched for old vue-i18n, $t, $i18n, createI18n, and useI18n references and found none.

@jevin98

Copy link
Copy Markdown
OwnerAuthor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Bravo.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@jevin98
jevin98 merged commit cbd4aaa into mainMay 14, 2026
@jevin98
jevin98 deleted the codex/wxt-i18n branch May 15, 2026 03:51
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@jevin98