These elements were heavily inspired by
<i18-n>, written by pkaske.
Using ES6 features, so take care in production.
# Assuming Node.js and Bower are already installedbower install --save f-i18n
The system consists of two elements working together:
<f-i18n> elements provides content or
value with translated strings of locale specified in their corresponding
The language to display isn't set on the
<f-i18n> elements but on the
<f-i18n> elements are automatically updated after the locale was changed on corresponding
- Initialize the
<!-- Will use the translations from `path/to/locales/default-de.json` --><!-- Will use the translations from `other/path/foobar-en.json` -->
<f-i18n>to get the translations.
<!-- Message from "default" domain, with key "welcome".Will display placeholder text until translation is loaded. --><!-- Message from "foobar" domain, with key "hello".Will not display any text, but set and notify "value" property. -->[[msgHello]]
From here on, documentation will only concern development of this component.
Element dependencies are managed via Bower. You can install that via:
npm install -g bower
Then, go ahead and download the element's dependencies:
Playing With Your Element
If you wish to work on your element in isolation, we recommend that you use Polyserve to keep your element's bower dependencies in line. You can install it via:
npm install -g polyserve
And you can run it via:
Once running, you can preview your element at
f-i18n is the name of the directory containing it.
Testing Your Element
Simply navigate to the
/test directory of your element to run its tests. If
you are using Polyserve:
The tests are compatible with web-component-tester. Install it via:
npm install -g web-component-tester
Then, you can run your tests on all of your local browsers via:
wct -l chrome will only run tests in chrome.
wct -p will keep the browsers alive after test runs (refresh to re-run).
wct test/some-file.html will test only the files you specify.