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

@instructure/i18nliner-canvas

v1.3.0

Published

i18nliner, canvas style

Downloads

3,010

Readme

canvas_i18nliner

i18nliner, canvas style

this will replace the i18n_tasks and i18n_extraction gems

.i18nrc files must glob for files to be included through the files property:

{
  "files": [
    {
      "pattern": "**/*.js",
      "processor": "js"
    },
    {
      "pattern": "**/*.{hbs,handlebars}",
      "processor": "hbs"
    }
  ]
}

.i18nrc files can include other directories that may in turn specify more files through their .i18nrc configuration file:

{
  "include": [ "relative/path/to/dir" ]
}

.i18nignore files can exclude files from processing relative to where they are defined (similar to .gitignore):

// file: app/.i18nignore
foo
bar/**/*.js

The above ignore file will exclude app/foo and app/bar/**/*.js.

Where to place ignore lists?

The scanner will always look for an .i18nignore adjacent to .i18nrc, but it will also discover and use any .i18nignore file found between the root and the target file:

app
├── .i18nignore
└── a
    ├── .i18nignore
    └── b
        └── c

A file under app/a/b/c/ is subject to exclusion according to rules found in both app/.i18nignore and app/a/.i18nignore.

Handlebars

Allowed forms:

<!-- inferred keys -->
{{t "Hello"}}
{{#t}}
  Hello
{{/t}}

<!-- explicit keys -->
{{t "hello" "Hello"}}
{{#t "hello"}}
  Hello
{{/t}}

<!-- explicit, external scope key -->
{{#t "#external.hello"}}
  Hello
{{/t}}