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

ngx-extract-i18n-merge-json

v1.0.9

Published

Extract and merge i18n JSON translation files for angular projects.

Downloads

44

Readme

Angular JSON extract i18n and merge

Based on ngx-extract-i18n-merge by @daniel-sc.

This extends Angular CLI to improve the i18n extraction and merge workflow. New/removed translations are added/removed from the target translation files. Additionally, translation files are normalized (pretty print, sorted by id) so that diffs are easy to read (and translations in PRs might actually get reviewed ;-) ).

Install

Prerequisites: i18n setup with defined target locales in angular.json - as documented here.

ng add ngx-extract-i18n-merge-json

Usage

ng extract-i18n # this replaces and extends the original builder

Configuration

In your angular.json the target extract-i18n that can be configured with the following options:

| Name | Default | Description | |------------------------------|-------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | browserTarget | Inferred from current setup by ng add | A browser builder target to extract i18n messages in the format of project:target[:configuration]. See https://angular.io/cli/extract-i18n#options | | outputPath | Inferred from current setup by ng add | Path to folder containing all (source and target) translation files. | | targetFiles | Inferred from current setup by ng add | Filenames (relative to outputPath of all target translation files (e.g. {"fr-FR": "messages.fr.json", "de-DE": "messages.de.json"). | | sourceLocale | Undefined | If this is set (to one of the targetFiles locales), new translations in that target file won't include the newPrefix prefix). | | sourceFile | messages.json. ng add tries to infer non default setups. | Filename (relative to outputPath of source translation file (e.g. "translations-source.json"). | | newPrefix | This prefix will be added to all new translations (e.g. @new). | | removeIdsWithPrefix | [] | List of prefix strings. All translation units with matching id attribute are removed. Useful for excluding duplicate library translations. | | collapseWhitespace | true | Collapsing of multiple whitespaces/line breaks in translation sources and targets. | | trim | false | Trim translation sources and targets. | | includeContext | false | Whether to include the context information (like notes) in the translation files. This is useful for sending the target translation files to translation agencies/services. When sourceFileOnly the context is retained only in the sourceFile. | | newTranslationTargetsBlank | false | When false (default) the "target" of new translation units is set to the "source" value. When true, an empty string is used. When 'omit', no target element is created. | | builderI18n | "@angular-devkit/build-angular:extract-i18n" | The builder to use for i18n extraction. Any custom builder should handle the same options as the default angular builder (browserTarget, outputPath, outFile, format, progress). | | verbose | false | Extended/debug output - it is recommended to use this only for manual debugging. |

Contribute

Feedback and PRs always welcome :-)

Before developing complex changes, I'd recommend opening an issue to discuss whether the indented goals match the scope of this package.