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

trifid-plugin-i18n

v3.0.3

Published

Trifid plugin for i18n support

Downloads

53

Readme

trifid-plugin-i18n

A Trifid plugin to add i18n support to Trifid.

Usage

Install this Trifid plugin using:

npm install trifid-plugin-i18n

The plugin needs to be added to the Trifid config under the plugins property. It should be loaded before the locals plugin and the template engine. In the following example order 5 is used which works for the default config where the locals plugin uses a higher order value. The config for the i18n package can be set using the config property. The directory configuration field is required, and should point to the directory where you i18n JSON files are stored. See the i18n list of configuration options for more details. Some default values are defined in the index.js file.

Example of configuration:

plugins:
  # […] your other plugins
  i18n:
    module: "trifid-plugin-i18n"
    order: 5
    config:
      directory: file:locales
      locales:
        - en
        - de
      # …other configuration fields