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

ng-localizer

v1.3.1

Published

A picker for find and create translate json files

Downloads

23

Readme

ng-localizer

The picker for search and create/edit translate json files.

Installation

Using npm:

$ npm install --dev ng-localizer

Add script to package.json:

"scripts": {
  "ng-localizer": "ng-localizer \"DIRECTORY_OR_FILE_SEARCH_KEYS\""
}

Using

Run

$ npm run ng-localizer

Use flag --full for search keys in whole project. Without it will search in only git change project Use flag --preserve-keys for preserve keys in project. Without it will delete unused keys

Config

You can customize autocreating config file in project's root (ng-localizer.config.json):

{
  "FILE_TYPES"   : ["ts", "html"],
  "LANGUAGES"    : ["ru", "en"],
  "KEY_REGEX"    : "'([aA-zZ0-9._\\-]*)' \\| translate|\\.instant\\('([aA-zZ0-9._\\-]*)'\\)|__\\('([aA-zZ0-9._\\-]*)'\\)",
  "PATH_JSON"    : "[aA-zZ0-9\\-_@]*\\/i18n\\/([aA-zZ0-9\\-_@]*)\\.",
  "CORE_MODULE_REGEX" : "\\.module.ts$",
  "ALLOW_CREATE" : true
}
  • FILE_TYPES - file types for search
  • LANGUAGES - for every key will generate file language
  • KEY_REGEX - default regular expressions for searching keys:
    • ([aA-zZ0-9._\\-]*)' \\| translate -> 'something.key' | translate
    • .instant\\('([aA-zZ0-9._\\-]*)'\\) -> '.instant('something.key')
    • __\\('([aA-zZ0-9._\\-]*)'\\) -> '__('something.key')
  • PATH_JSON - path for localization json files
  • CORE_MODULE_REGEX - regexp for find core modules
  • ALLOW_CREATE - allow create not exist files