feat: add i18n-inspect

[Polkilof]

A dev-only module for editing @nuxtjs/i18n translations in the running page. Alt-click a string, edit it, and the change is written straight into the locale JSON file — no backend, and nothing registered in a production build.

Live demo (StackBlitz, runs the module for real): https://stackblitz.com/github/Polkilof/nuxt-i18n-inspect
Overview page: https://polkilof.github.io/nuxt-i18n-inspect/
npm: https://www.npmjs.com/package/nuxt-i18n-inspect
Tested on Nuxt 3.21 with @nuxtjs/i18n 9, and on Nuxt 4.5 with @nuxtjs/i18n 10.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 21802984-600e-4893-b897-c927b69c3e2b

📥 Commits

Reviewing files that changed from the base of the PR and between 165a4a4 and 7f0a794.

⛔ Files ignored due to path filters (1)

• icons/i18n-inspect.svg is excluded by !**/*.svg

📒 Files selected for processing (1)

• modules/i18n-inspect.yml

Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.

---

📝 Walkthrough

Walkthrough

Added i18n-inspect metadata to the Nuxt Devtools module registry. The metadata includes package and repository links, description, icon, website, maintainer, Devtools classification, third-party designation, and Nuxt >=3.0.0 compatibility.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 7f0a7

This change adds the i18n-inspect module metadata and icon without any evidenced merge-blocking correctness, security, availability, or deployment risk; no actionable merge-blocking risk remains.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[Polkilof]

The autofix failure here is unrelated to this PR.

That job runs pnpm sync, which refetches live metadata for every module in
the registry rather than only the entry being added. The failure in the log is
on an unrelated module (windicss); this PR adds a single module entry and
touches nothing else.

The required ci check is green.

I've deliberately left .github/workflows/autofix.yml alone. Forcing that step
to pass would let the following autofix-ci step commit a diff built from a
partially synced state, which risks writing bad metadata for whichever modules
failed to fetch — the failure is doing useful work there.

Happy to rebase or adjust the entry if anything needs changing. If it would be
useful, I can open a separate issue about sync isolating failures per module
so one bad entry doesn't fail the whole batch.