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-extract-i18n-reverse

v0.0.3

Published

Extract and reverse-merge i18n AMB translation files for angular projects.

Downloads

4

Readme

npm Coverage Status CodeQL

Angular extract i18n and reverse-merge

This extends Angular CLI to improve the i18n extraction. It adds functionality to reverse-merge target translation files back to source code

Install

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

ng add ng-extract-i18n-reverse

Usage

ng extract-i18n # yes, same as before - this replaces 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 | | format | Inferred from current setup by ng add | Any of xlf, xlif, xliff, xlf2, xliff2 | | 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. ["messages.fr.xlf", "messages.de.xlf"]). | | sourceFile | messages.arb. ng add tries to infer non default setups. | Filename (relative to outputPath of source translation file (e.g. "translations-source.arb"). | | targetPath | none | Path to folder containing target file for further comparison | | targetFile | messages.en-US.arb. ng add tries to infer non default setups.| Filename (relative to targetPath of target translation file which is used for further comparison with source file (e.g. "translations-target.arb"). | | check | false. | Whether to compare target file with source file to find differences |

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.