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

@tomuench/i18n-translate

v0.0.5

Published

An Element-Extension to translate its content.

Downloads

2

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

tomuenchtomuench

Keywords

web-componentswebcomponentslanguagei18n

Readme

i18n-translate: Web-Component for Translation

An Element-Extension to translate it's content. It is written with Vanilla-JS and HTML5-Standards. It recognizes the language of the browser and searching up your translation-keys in a dictonary. You can provide your JSON-Dictonary on your own.

It's not as complex as other i18n-components, but it is simple and extendable. This project is at an early stage and needs further development.

    <p>Firstname: <i18n-translate>person.firstname</i18n-translate></p>
    <p>Lastname: <i18n-translate>person.lastname</i18n-translate></p>
    <p>Not-Known: <i18n-translate>unkown</i18n-translate></p>

1. Requirements

First of all make sure you have the Polymer CLI installed. Then run polymer serve to serve your element locally.

2. Configuration

You had to include your Language-DB as a JSON-File into the HTML-Document. Make sure you have tagged it with i18n-data. For example your document looks like this:

<head>
  <link i18n-data rel="import" href="language.html">
</head>
<i18n-translate>your.key.to.translate</i18n-translate>

So your language.html should contain the following:

{
  "en": {
    "your": {
      "key": {
        "to": {
          "translate
        }
      }
    }
  }
}

3. Installation

npm i @tomuench/i18n-translate

Development

In the following section it is described how to extend this web-component.

Viewing Your Element

$ polymer serve --open

Running Tests

$ polymer test

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Credits

This web-component belongs to the EFRE research-project Vet:ProVieh from the University of Applied Science Osnabrück.

Thanks to Adam Bien for his inspriation in the blog-entry http://www.adam-bien.com/roller/abien/entry/simplest_possible_internationalization_with_vanilla.

License

MIT