Skip to content
PN Scripts

Developer tools

Keyglint

by PN Scripts

A VS Code extension that shows the translated text next to every key, reports keys missing in any locale and adds them to every Laravel, vue-i18n or i18next file with one command.

  • Visual Studio Code extension API
  • JavaScript
  • Laravel lang files
  • vue-i18n
  • i18next
  • Coming soon

Coming soon

Not published on its store yet, so there is no buy or download link. PN Scripts does not take payment for it here.

Developer tools
Blade view with translated values after each key and a hover listing English and Bulgarian

What it solves

The gap

In a multilingual project a key like auth.failed says nothing about the text behind it, and a key forgotten in one locale stays invisible until a user sees the raw key on the page.

What it is

Keyglint shows the real text beside each key, flags every key missing in any locale while you code, and fills the gaps in all locale files at once without breaking their formatting.

How you use it

Read code with the real words in it and catch missing translations before release instead of after.

For Laravel and JavaScript developers who ship in more than one language, Keyglint is a lightweight VS Code extension that understands both PHP lang arrays and JSON locale files in the same project.

Who it is for

Use it when

  • Adding Bulgarian or another language to an existing Laravel application
  • Keeping vue-i18n or i18next locale files in sync during feature work
  • Reviewing a pull request for keys that were added in one language only

Built for

  • Laravel and PHP developers
  • Vue and React developers using vue-i18n or i18next

What is inside

See the words, not the keys

After each key Keyglint prints its text in grey, shortened to fit. Missing locales are named in yellow. The command Choose Locale for Inline Values switches the whole editor to Bulgarian, German or any other locale you have.

Find what is missing

Every key used in code is checked against every locale. Gaps show up as warnings, keys defined nowhere as errors, and the Missing Translations view lists them per locale, including keys that exist in one locale only.

Fix it in one step

On a missing key, the quick fix asks for the text in each locale that lacks it, prefilled with the source text, and writes it into the matching file. Nested arrays and objects are created where needed, and new locale files are created if they do not exist yet.

Fits Laravel and JavaScript projects

Laravel lang/*.php groups with subfolders, lang/vendor package files and lang/*.json strings are read the way Laravel resolves them. vue-i18n and i18next JSON files, nested or flat, and i18next namespaces such as checkout:pay are supported too.

Specs

Availability
Coming soon
Vendor
PN Scripts
Type
Extension
Platforms
JavaScript, Laravel, PHP
Pricing
One-time purchase Price to be announced.
License
Proprietary
Deployment
Download (.vsix file to install in VS Code)
Maturity
v1.0.0

Compatibility

Platform or runtime Supported versions Tested up to
Visual Studio Code 1.85 or newer 1.141 (.vsix installed from the command line; not run in an open window)
Node.js (to run the tests) 20 or newer 22.23

Stack

  • Visual Studio Code extension API
  • JavaScript
  • Laravel lang files
  • vue-i18n
  • i18next

Keyglint is coming soon

It is finished and tested. It is not on sale yet; this page will say where to get it when it is.

Coming soon

Not published on its store yet, so there is no buy or download link. PN Scripts does not take payment for it here.

Questions

A Visual Studio Code extension for translation keys: inline values, hovers, go to definition, missing-key diagnostics, a view of missing keys per locale and a command that adds a key to every locale file.

Visual Studio Code 1.85 or newer and a project with translation files in folders such as lang, resources/lang, locales or i18n. Other folders can be set in the settings. No other extensions or packages are needed.

It does not translate text automatically, does not read YAML, PO or XLIFF files, and cannot check keys built at runtime. It is not published on the VS Code Marketplace; you install the .vsix file. It was not exercised in an open VS Code window during testing.

It is written in plain JavaScript with its own PHP-array and JSON parsers, and tested with Node.js on Laravel, vue-i18n and i18next fixture projects in English and Bulgarian, including the extension code through a test double of the VS Code API. Created with AI assistance; the parsers, key resolution, file edits and the extension's providers and commands were checked by PN Scripts with automated Node.js tests on English and Bulgarian fixture projects.

It is not on sale yet. When it is, this page will link to the store; PN Scripts does not take payment on this site.