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

@bud-tools/localization-manager

v0.0.1

Published

BudTools localization manager API.

Downloads

1

Readme

Description

The @bud-tools/localization-manager package is used easily create localizations of BudTools and BudTools extensions for different languages. It has two main use cases.

First, it allows to extract localization keys and default values from nls.localize calls within the codebase using the nls-extract BudTools-CLI command. Take this code for example:

const hi = nls.localize('greetings/hi', 'Hello');
const bye = nls.localize('greetings/bye', 'Bye');

It will be converted into this JSON file (nls.json):

{
  "greetings": {
    "hi": "Hello",
    "bye": "Bye"
  }
}

Afterwards, any manual or automatic translation approach can be used to translate this file into other languages. These JSON files are supposed to be picked up by LocalizationContributions.

Additionally, BudTools provides a simple way to translate the generated JSON files out of the box using the DeepL API. For this, a DeepL free or pro account is needed. Using the nls-localize command of the BudTools-CLI, a target file can be translated into different languages. For example, when calling the command using the previous JSON file with the fr (french) language, the following nls.fr.json file will be created in the same directory as the translation source:

{
  "greetings": {
    "hi": "Bonjour",
    "bye": "Au revoir"
  }
}

Only JSON entries without corresponding translations are translated using DeepL. This ensures that manual changes to the translated files aren't overwritten and only new translation entries are actually sent to DeepL.

Use budtools nls-localize --help for more information on how to use the command and supply DeepL API keys.

For more information, see the internationalization documentation.

Additional Information

License

Trademark

"BudTools" is a trademark of the Eclipse Foundation https://www.eclipse.org/budtools