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

i18n-express

v1.1.3

Published

A simple i18n middleware for Express.js.

Downloads

6,252

Readme

i18n-express

Build Status npm version

A simple i18n middleware for Express.js This module just reads all the .json files in a directory. Then calculates the user lang and exposes "texts" variables in your views with the texts in that json.

By default, the user will see the site in the language set by the cookieLangName session. If the session is not set, the language set by the browser will be used.

If the user wants to set the language to spanish for example, he would have to visit http://site.com/?clang=es (clang is defined at paramLangName).

This can be done by using a html 'select' or any other means you want. Once that is done, the cookieLangName session will be updated with the new language and the user will forever see the site in the new language until he decides to set a new language again.

NOTE: When using this module, we recommend also using the geolang-express module, which sets the cookieLangName session to a language based on the visit IP address.

Requirements

  • Node >= 0.12
  • Express.js

Instalation

$ npm install i18n-express

Usage

var i18n=require("i18n-express");

app.use( i18n(options) );

Options

  • translationsPath : (default: i18n) The path where you store translations json files.
  • cookieLangName : (default: ulang) If you provide a cookie name, try to get user lang from this cookie.
  • browserEnable : (default: true) If enabled, try to get user lang from browser headers.
  • defaultLang : (default: en) If all others methods fail, use this lang.
  • paramLangName : (default: clang) Get param to change user lang. ej: visiting 'example.com?clang=es' the lang switchs to 'es'
  • siteLangs : (default: ['en']) Array of supported langs. (posbile values for clang and json files)
  • textsVarName : (default: texts) Name of variable which holds the loaded translations.

Example

Create a directory "i18n" with .json files for each lang. Ej:

  • en.json
  • es.json
  • en-us.json

With translations like this (en.json):

{
"WELCOME_MSG": "Hi! Welcome!",
"CONTACT_TEXT": "More bla"
}

In your Express app.js:

var express = require('express');
var path = require('path');
var cookieParser = require('cookie-parser');
var bodyParser = require('body-parser');
var i18n=require("i18n-express"); // <-- require the module

var indexRoutes = require('./routes/index');

var app = express();

// view engine setup
app.set('views', path.join(__dirname, 'views'));
app.set('view engine', 'ejs');
app.use(cookieParser());
app.use(express.static(path.join(__dirname, 'public')));
app.use(session({
  secret: 'secret',
  saveUninitialized: true,
  resave: true
}));

app.use(i18n({
  translationsPath: path.join(__dirname, 'i18n'), // <--- use here. Specify translations files path.
  siteLangs: ["en","es"],
  textsVarName: 'translation'
}));
...

app.use('/', indexRoutes);

module.exports = app;

...

Now in your ejs view you have texts object and lang variable with the active language:

<div>
  Choose your language:
  <ul>
    <li><a class="<%=(lang=="es"?"active":"")%>" href="/?clang=es">Spanish</a></li>
    <li><a class="<%=(lang=="en"?"active":"")%>" href="/?clang=en">English</a></li>
  </ul> 

	<p><%=translation.WELCOME_MSG%></p>
  
</div>

Or in your handlebars view:

<div>
  Choose your language:
  <ul>
    <li><a href="/?clang=es">Spanish</a></li>
    <li><a href="/?clang=en">English</a></li>
  </ul> 

	<p>{{translation.WELCOME_MSG}}</p>

</div>

License

MIT

Author