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

@graasp/translations

v1.42.0

Published

Graasp Translations

Downloads

3,091

Readme

Graasp Translations

gitlocalized

Repo containing translations for graasp.

Using translations in your app

To use translations in your app you should:

  • Create the translation config by calling buildI18n('your_app_name') and eventually changing the language used with i18next.changeLanguage(new_language).
  • Make sure the namespace you want to use exists. If it does not exist you should create it by following the information in the section bellow

Adding support for a new app

In this section we create a new translation namespace that will contain your app's translations.

  • Create a file with constant keys in src/constants/your_app_name.ts with the following content:
export const MY_APP_NAME = {
  WELCOME_MESSAGE: 'Hello World',
  // add more keys here ...
};
  • Create a file for each supported language in src/langs/<language-initials>/your_app_name.ts with the following content:
import { MY_APP_NAME } from "../../constants/your_app_name";

export default {
    [MY_APP_NAME.WELCOME_MESSAGE]: 'Hello World',
    // other translations here ...
};
  • Finally, add your translations to the exising src/langs/index.ts file.

Documentation

i18next Namespaces i18next Namespaces