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

@dao-dao/i18n

v2.4.0-rc.8

Published

[Internationalization](https://www.w3.org/standards/webdesign/i18n) (i.e. translation) system for the DAO DAO UI.

Downloads

18

Readme

@dao-dao/i18n

Internationalization (i.e. translation) system for the DAO DAO UI.

Contributing a translation

See ./locales/en/translation.json. Make a folder with your language's (ISO 639-1)[https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes] code and place your translation there. When you're done, make sure to add your language's code to the config.i18n.locales array in the ./next-i18next.config.js file.

Translation notes

Keep it precise and pithy, in that order; people's businesses depend on understanding what this software does. Within those constraints, keep it as casual and informal as possible.

Comparing diffs

To compare two translation files to see what keys have been added, removed, and modified, run yarn get-diff <locale1.json> <locale2.json>. For example, to see what is missing from the Spanish translation that exists in the English translation, run the following command from this folder:

yarn get-diff locales/es/translation.json locales/en/translation.json

When comparing two different languages, the added and removed keys will be helpful in figuring out what needs to change, and the modified keys will be helpful in comparing the translations' accuracies.

When comparing two versions of the same language, the added and removed keys will be helpful in figuring out what needs to be translated, and the modified keys will be helpful in figuring out what needs to be updated.