npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

extract-gettext

v1.0.1

Published

Extract gettext strings from __('literal') and __n('single', 'plural', n ) functions in any source

Downloads

6

Readme

extract-getext

Build Status

Extract gettext strings from __('literal') and __n('single', 'plural', n ) functions in any source. This module currently only looks for the __ and __n function signatures.

The format produced by this package is similar to the output of xgettext, containing all strings in one flat array. When outputting a .json file, the format is usable by i18next-conv.

Install

npm install extract-gettext

Usage

CLI

extract-gettext -o <output file> -x <exclude pattern> **/*.js

API

( as taken from the "test" )


    let scan = require("extract-gettext");

    function x(__, __n) {
        __('This is a singular translation %s', 'replacement');
        __('Plain old singluar');
        __n('single', 'plural', 1, 'cats');
        __n('error, but it works');
        __('one on the same line');
        __('as the other');
        __('even mixing goes');
        __n('like this', 'or that', 3);
        __('duplicate strings are filtered');
        __('duplicate strings are filtered');
        __('duplicate strings are filtered');
        __("Oh, and by the way: don't fail on this!");
        __('Oh, and by the way: this don\'t fly either!');
        __n('What\'s in a count', 'Won\'t you count it', 3);
        __('Accept (parenthesis) in a string');
        __n("we can have some (parenthesis)", "we can have one (parenthesis)", 3);
        __('a "string" can have quotes');
        __("a 'string' can have quotes");
        __("a string can \" mix a quote in various ways");
    }
    
    let strings = scan([__filename]);
    
    console.log(strings);

background

The tool xgettext has good support for javascript, and extracts strings faster then this tool, but is hardcoced for the _('literal') notation.

Some other good tools exist, such as:

roadmap and future development

Please drop me a personal note on matthijsatischendotnl if you want to use this and I need to fix things.