Skip to content
Manage vue-i18n localization with static analysis
TypeScript JavaScript Vue Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci
demo
docs
src
tests
.editorconfig
.gitignore
LICENSE
README.md
deploy.sh
jest.config.js
package-lock.json
package.json
tsconfig.json
tslint.json

README.md

vue-i18n-extract

NPM Version Downloads CircleCI Status Known Vulnerabilities Maintainability


vue-i18n-extract is built to work with your Vue.js projects using vue-i18n. When run vue-18n-extract analyses your Vue.js source code for any vue-i18n key usages (ex. $t(''), $tc(''), ...) as well as your language files (ex. de_DE.js, en_EN.json, ...), in order to:

  • I18NReport keys that are missing in the language files.
  • I18NReport unused keys in the language files.

📖 Documentation

Check the official documentation here: https://pixari.github.io/vue-i18n-extract/

❗️ Issues

I'm sure you'll find bugs and when you do it would be great if you'd could report them here.

💪 Contribution

The project is still in its early stages and in progress. I think there's no need for guidelines yet, so feel free to contribute or give feedback as you prefer.

PLEASE: don't forget to update the documentation if you change the API. (https://github.com/pixari/vue-i18n-extract/tree/master/docs)

©️ License

MIT

You can’t perform that action at this time.