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

mil-i18

v1.2.0

Published

I18 Webcomponent following open-wc recommendations

Downloads

5

Readme

<mil-i18>

'mil-i18' is localization webcomponent. It uses local translation files. Language is set according to the user browser defaults.

This webcomponent follows the open-wc recommendation.

Demo: https://stackblitz.com/edit/mil-i18-example?file=index.js

Installation

npm i mil-i18 --save

Usage

<script type="module">
  import 'mil-i18/mil-i18.js';
  import { ifDefined } from 'lit-html/directives/if-defined';
</script>

<mil-i18 namespace="app" @translatedKeys="${(e)=>{this._i18=e.detail}}"></mil-i18>

<p>${ifDefined(this._i18.key1)}</p>

File format

{
"key1":"translation1",
"key2":"translation2"
}

Attributes

| Property | Type | Default | Description | | ------------------ | ------ | --------------------- | --------------------------------------------------------------------------------------------------------------------------- | | allowedLanguages | Array | ['en', 'fr'] | Languages for which there are translations files. Other languages will use the fallbackLanguage value | | fallbackLanguage | String | 'en' | Fallback language in case the user default browser or the forcedLanguage values are not part of the allowedLanguages array. | | forcedLanguage | String | '' | 'Forces language detection to a specific language' | | namespace | String | 'namespaceValue' | 'Json language file name' | | path | String | './assets/locales/' | Path to the JSON language file. | | |

Events

@translatedKeys: fired when the language file is loaded. File content is exposed in e.detail.

Linting with ESLint, Prettier, and Types

To scan the project for linting errors, run

npm run lint

You can lint with ESLint and Prettier individually as well

npm run lint:eslint
npm run lint:prettier

To automatically fix many linting errors, run

npm run format

You can format using ESLint and Prettier individually as well

npm run format:eslint
npm run format:prettier

Local Demo with es-dev-server

npm start

To run a local development server that serves the basic demo located in demo/index.html

npm start:compatibility

To run a local development server in compatibility mode for older browsers that serves the basic demo located in demo/index.html