JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 50980
  • Score
    100M100P100Q205908F
  • License MIT

Gettext extractor for JavaScript, TypeScript, JSX and HTML

Package Exports

  • gettext-extractor
  • gettext-extractor/dist/builder
  • gettext-extractor/dist/builder.js
  • gettext-extractor/dist/html/parser
  • gettext-extractor/dist/html/parser.js
  • gettext-extractor/dist/html/selector
  • gettext-extractor/dist/html/selector.js
  • gettext-extractor/dist/html/utils
  • gettext-extractor/dist/html/utils.js
  • gettext-extractor/dist/index.js
  • gettext-extractor/dist/js/extractors/comments
  • gettext-extractor/dist/js/extractors/comments.js
  • gettext-extractor/dist/js/extractors/common
  • gettext-extractor/dist/js/extractors/common.js
  • gettext-extractor/dist/js/parser
  • gettext-extractor/dist/js/parser.js
  • gettext-extractor/dist/js/utils
  • gettext-extractor/dist/js/utils.js
  • gettext-extractor/dist/parser
  • gettext-extractor/dist/parser.js
  • gettext-extractor/dist/utils/content
  • gettext-extractor/dist/utils/content.js
  • gettext-extractor/dist/utils/output
  • gettext-extractor/dist/utils/output.js
  • gettext-extractor/dist/utils/validate
  • gettext-extractor/dist/utils/validate.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (gettext-extractor) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Gettext Extractor Tests Status

A flexible and powerful Gettext message extractor with support for JavaScript, TypeScript, JSX and HTML

It works by running your files through a parser and then uses the AST (Abstract Syntax Tree) to find and extract translatable strings from your source code. All extracted strings can then be saved as .pot file to act as template for translation files.

Unlike many of the alternatives, this library is highly configurable and is designed to work with most existing setups.

For the full documentation check out the Github Wiki.


Installation

Note: This package requires Node.js version 20 or higher.

Yarn

yarn add gettext-extractor

NPM

npm install gettext-extractor

Getting Started

Let's start with a code example:

const { GettextExtractor, JsExtractors, HtmlExtractors } = require('gettext-extractor');

let extractor = new GettextExtractor();

extractor
    .createJsParser([
        JsExtractors.callExpression('getText', {
            arguments: {
                text: 0,
                context: 1
            }
        }),
        JsExtractors.callExpression('getPlural', {
            arguments: {
                text: 1,
                textPlural: 2,
                context: 3
            }
        })
    ])
    .parseFilesGlob('./src/**/*.@(ts|js|tsx|jsx)');

extractor
    .createHtmlParser([
        HtmlExtractors.elementContent('translate, [translate]')
    ])
    .parseFilesGlob('./src/**/*.html');

extractor.savePotFile('./messages.pot');

extractor.printStats();

A detailed explanation of this code example and much more can be found in the Github Wiki.


Contributing

From reporting a bug to submitting a pull request: every contribution is appreciated and welcome. Report bugs, ask questions and request features using Github issues. If you want to contribute to the code of this project, please read the Contribution Guidelines.