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

@shipyardsuite/i18n-manager

v0.1.3

Published

A simple to i18n Module for JavaScript front- and back-end.

Downloads

9

Readme

i18nManager

Codacy branch coverage Codacy branch grade GitHub last commit (branch) GitHub issues GitHub npm (scoped)

A simple to i18n Module for JavaScript front- and back-end.

Installation

$ npm i --save @shipyardsuite/i18n-manager

Usage

Perquisite

  1. Create a folder called i18n in your applications root folder.
  2. Create translation files named after the short form of the language and an index.js file in the folder,
  3. Import the translation files into the index file.

EXAMPLE FILES:

./i18n/de.js

export const de = {
    test:
    {
        firstMessage: "Hallo Welt!",
        secondMessage: "Es {val}."
    }
};

./i18n/en.js

export const en = {
    test:
    {
        firstMessage: "Hello World!",
        secondMessage: "This {val}."
    }
};

./i18n/index.js

import { de } from './de';
import { en } from './en';

export { de, en };
export default { de, en };

Getting translations

1. Import the module.

ES6:

import i18nManager from "@shipyardsuite/i18n-manager";

NodeJS:

const i18nManager = require("@shipyardsuite/i18n-manager");

2. Create an instance, and call the determined language (en, de, ...) in the constructor.

const translations = new i18nManager();

3. Call the message according to the json path you set up in the translation file.

translations.message("test.sentence");

Or, if you need to supply a value

translations.messageWithValue("test.sentence", value);

5. Your output now should show the selected message, or [MISSING] if you did not set the right path.

License

This project is released under the Apache version 2 license.