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

@captaincool/locale-key-generator

v3.0.1

Published

## Installation

Downloads

434

Readme

Locale Key Generator

Installation

Install the package via npm

npm install -g @captaincool/locale-key-generator

Configuration

By default, keys will be exported based on the contents of config.json. To use a custom configuration, supply its path using the --config argument during execution

locale-keys export -i ./content -o ./output --config=customConfig.json

Usage

# generate locale files for all contexts inside the 'content' directory and output them to 'output'
locale-keys export -i ./content -o ./output

# generate locale files for a specific context
locale-keys export -i ./content -o ./output --contexts=shared,web:feature

# lint the contents of the 'content' directory
locale-keys lint -i ./content

Options

| Option | Default | Description | | --------------------- | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | baseLanguage | en_US | Files with this code in the suffix of the filename will be treated as the base language. Any files which don't contain a base file will be discarded. | | outputFormat | json | The desired export format. Possible values are json or xliff | | contextDelimiterKeys | : | How to specify contexts messages belong to | | contextDelimiterFiles | __ | How to specify contexts in the final output files | | localeRegionExp | /[a-z]{2}_[A-Z]{2}/ | The pattern to determine locale | | keyMatchExp | /[\\w]+/ | The style pattern contexts and message keys should enforce | | ignoreFiles | ['.DS_STORE'] | A list of files to be ignored by the parser | | filenameSuffix | | A fixed string to apply at the end of the exported file | | reservedContext | messages | Files with this name will be rolled into the same context as their parent. For example, messages contained inside "some/feature/messages.en_US.json" will be namespaced as "some:feature" | | indent | 2 | Enforce an indentation style either via number of spaces or "tab". Accepts a number or the value "tab"|