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

@cbourgois/simonsays

v1.0.7

Published

Find translations used in AngularJS project

Downloads

17

Readme

SimonSays

npm version Dependencies Dev Dependencies

"Jacques a dit" Like.

simonsays help you: to find translations key used in your project and:

  • check if translations are availables in your project sources
  • search translations in another project
  • rewrite complete translations files (and support prefixing translations key)

To do it, simonsays parse your javascript and html files to detect angular-translate usages.

Simonsays detect :

  • $translate and $translate.instant calls in your javascript files,
  • translate directives in your HTML files,
  • translate filter usages in your HTML files.

We use @babel/parser to parse your javascript code in AST and we have ported $interpolate and $ParseProvider from AngularJS (code available here).

Simonsays supports translations defined in JSON or XML files.

Installation

With yarn:

yarn add @cbourgois/simonsays

or

With npm:

npm install @cbourgois/simonsays

Usage

CLI Usage

With npx:

npx @cbourgois/simonsays --help

Check

Compatibles options: --locale, --module, --output.

To check used translations:

simonsays check <sourcePath>

Search

simonsays search <sourcePath> <projectPath>

To search used translations (only used translations will be reported):

simonsays search <sourcePath> <projectPath>

To search used translations and retrieve all (already present translations + used translations):

simonsays search <sourcePath> <projectPath> --all

To overwrite existing translations by the project translations:

simonsays search <sourcePath> <projectPath> --merge

Compatibles options: --all, --merge, --locale, --module, --output.

Rewrite

To rewrite JSON translations file:

simonsays rewrite <sourceDir> <projectPath>

To rewrite JSON translations file and prefix translations (AngularJS code and html will be overwritten):

simonsays rewrite <sourceDir> <projectPath> --prefix=ng_

Compatibles options: --all, --merge, --locale, --module, --output, --prefix.

CLI Options

AngularJS module

By default, the script parse all the source path and will generate one, and only one translation file. If you want, you can specify the --module option to parse/generate translations for each AngularJS module contained in the source path.

For example:

simonsays check <sourcePath> --module

Locale

By default, simonsays target the fr_FR locale, but you can change it by specifying --locale option.

For example:

simonsays check <sourcePath> --locale=en_GB

Output

You can specify an output format from the following:

  • summary (default) : output a table with the results
  • text : output a table with num of results
  • json : output a json
  • silent : no output

For example:

simonsays search <sourcePath> <projectPath> --output=text

About

This project embed some portions of AngularJS source code (see ./src/angularjs/**).