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

i18n-po-json

v1.1.0

Published

i18n .po to .json file converter

Downloads

1,898

Readme

i18n-po-json

pojson is a CLI tool to convert gettext PO format to JSON i18n entry list.

Command-line usage

To install pojson system-wide, run:

$ sudo npm install -g i18n-po-json

Then you can use it like this:

$ pojson --help
i18n PO -> JSON converter

Options:
   -h / --help                            Show this help
   -s / --src FILE                        Define input JSON file name. Defaults
                                          to stdin.
   -o / --output FILE                     Define output POT file name. If a file
                                          already exists, it's contents will be
                                          overwritten. Defaults to stdout.
   -n / --withOccurences                  Include occurences info into JSON file,
                                          parsed from "#: ..." comments.
   -c / --withComments                    Include comments into JSON file, parsed
                                          from "#. ..." comments.
   -p / --prettify                        Pretty-print JSON output.
   -m / --withMeta["full" | "plural"]     Include parsed PO header or plural form
                                          into JSON file. Add all header values
                                          without any params provided. Possable
                                          values "" | "full" | "plural"

By default pojson accepts input PO file from stdin. Output defaults to stdout, so you can use standard unix stream redirection syntax. Errors and warnings are printed to stderr.

Usage example:

$ cat ~/some/path/en_AE.po | pojson -p --withMeta plural > /dev/null

API usage

Take a look at CLI entry point - index.ts. Usage of the one and only convert function is pretty straightforward and there you will find all examples you ever need. Also you may want to take a look on unit tests to know how to collect errors and warnings efficiently when using convert programmatically.

Contributing

i18n-po-json uses github-flow to accept & merge fixes and improvements. Basic process is:

  • Fork the repo.
  • Create a branch.
  • Add or fix some code.
  • Run Karma testing suite with npm run test and make sure nothing is broken
  • Add some tests for your new code or fix broken tests.
  • Run npm run build to build pure-js distribution files.
  • Commit & push.
  • Create a new pull request to original repo.

Pull requests with failing tests will not be accepted. Also, if you add or modify packages to package.json, make sure you use yarn and update yarn.lock.