Skip to content

aurelia/i18n

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
doc
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Aurelia

License: MIT npm Version CircleCI Discourse status Twitter Discord Chat Coverage Status

aurelia-i18n

This library is part of the Aurelia platform and contains a plugin that provides i18n support. Under the hood it uses the i18next library.

You can find complete documentation on setup and usage in the official Aurelia Developer Hub

To keep up to date on Aurelia, please visit and subscribe to the official blog and our email list. We also invite you to follow us on twitter. If you have questions look around our Discourse forums, chat in our community on Discord or use stack overflow. Documentation can be found in our developer hub.

Polyfills

None

Platform Support

This library can be used in the browser only.

Building The Code

This library can be used in the browser and node.

Building The Code

To build the code, follow these steps.

  1. Ensure that NodeJS is installed. This provides the platform on which the build tooling runs.
  2. From the project folder, execute the following command:
npm install
  1. To build the code, you can now run:
npm run build
  1. You will find the compiled code in the dist folder, available in various module formats and the typings inside the typings subfolder.

Running The Tests

To run the unit tests, first ensure that you have followed the steps above in order to install all dependencies and successfully build the library. Once you have done that, proceed with these additional steps:

  1. For single execution run:
npm run test
  1. For continuous tdd style:
npm run test-watch
  1. You can find the coverage report built after each test run:
cat /test/coverage-jest/index.html