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

openl10n-to-bazingatranslator

v0.1.1

Published

Script to convert openl10n .yml files to files expected by bazinga-translator

Downloads

5

Readme

Mapado OpenL10n to Bazinga-Translator Build Status

Node script to convert YAML files generated by OpenLocalization CLI tool to files used by Bazinga Translator

Installation

npm install openl10n-to-bazingatranslator

or

yarn install openl10n-to-bazingatranslator

Usage

  • First make sure you have your .yml files somewhere in your project
  • Run ./node_modules/.bin/openl10n-to-bazinga-translator --format=[format] --target=[targetDirectory] --source=[sourceDirectory]

Where :

  • format is the expected format of the files. It depends on how you will use bazinga-translator. Supported formats are json and js.
  • [targetDirectory] is where you want the bazinga files stored.
  • [sourceDirectory] is where your .yml files are stored

Example

In your app/translations files, you have the following files: messages.en.yml messages.fr.yml anotherdomain.en.yml anotherdomain.fr.yml

In this configuration, you have 2 translations domains, messages and anotherdomain, and for each of these domains, two locales, en and fr

To generate the bazinga-translator as JSON files, you would run ./node_modules/.bin/openl10n-to-bazinga-translator --format=json --target=public/translations --source=app/translations

You would then have the following structure:

  • public/
    • translations/
      • messages/
        • en.json
        • fr.json
      • anotherdomain/
        • en.json
        • fr.json