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

angular-jed

v1.2.0

Published

Angular wrapper for Jed

Downloads

3

Readme

Angular-Jed

Angular wrapper for Jed.

Check out the gh-pages branch to see a working example.

Installation

npm install --save angular-jed

or

bower install angular-jed

Usage

Configuration

When running your app it's on you to set the language and the path to the translations files.

angular.module('myApp', ['jed'])
  .run(['i18n', function(i18n) {
    i18n.setTranslationPath('/path/to/translations')
      .setLang('fr_FR');
  }]);

Controllers

The service provides a loadPage method to load a page translation file. The method returns a promise to make sure the translations methods can be used safely.

angular.module('myApp')
  .controller('Video', [
    '$scope',
    'i18n',
    function($scope, i18n) {
      i18n.loadPage('video').then(function() {
        $scope.translatedText = i18n._('This text will be translated');
      });
    }
]);

Common translations

You can load common translations (eg. for directives) which will add to the current translations loaded. Returns a promise.

angular.module('myApp')
  .directive('footer', ['i18n', function(i18n) {
    i18n.loadCommon('footer').then(function() {
      message = i18n._('This text will be translated');
    });
  }
]);

Translations

Filter

In the views you can use the trans filter:

<h1>{{ 'Translated title here'|trans }}</h1>
<h2>{{ 'There is one cat'|trans:{plural: 'There are several cats', count: nbrOfCats, none: 'There are no cats'} }}</h2>

Options:

  • singular Singular text
  • plural Plural text
  • none (optionnal) Text to display when count is 0
  • count
  • placeholders objects containing the variables to interpolate. The count is automatically added.

Directive

A trans directive is available for more complex plural:

<trans singular="There is one %obj%" plural="There are %number% %objs%" none="No %objs%" count="nbr" placeholders="{number: nbr, obj: object, objs: objects}"></trans>

The attributes are the same as the options for the filter.

API

  • setTranslationPath(path) Set the translation path to retrieve the translation files
  • setLang(value) Sets the language of the app
  • getLang Returns the current language of the app
  • setDefaultLang(value) Sets the default language
  • ready Returns a promise resolved when the service has loaded the initial file
  • loadPage(page) Load a page translations. Returns a promise
  • loadCommon(name) Load common translations (footer, header...). Returns a promise
  • _(key) Simple translation
  • _n(singular_key, plural_key, value) Translation for plural

Translation files

The files MUST be named with the name of the page or directive and the language: name-fr_FR.json. For example calling i18n.loadPage('video') will load the file video-fr_FR (or whatever language the site is in).

The translations files are cached so they won't be loaded twice. The cache is only a js variable so it just lives during the angular app life.

If the translations files are not found the service falls back to the a default language. If even the default language file isn't found the translations method juste returns the given keys.

Known issue

The domains are not usable for now. The loadCommon method merges the messages with the current page loaded, so everything falls into the page domain.