JSPM

tixtec-date-names

0.1.4
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1
  • Score
    100M100P100Q19404F
  • License MIT

Repository of localized month and day names

Package Exports

  • tixtec-date-names
  • tixtec-date-names/de
  • tixtec-date-names/en
  • tixtec-date-names/fr

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (tixtec-date-names) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

date-names

Repository of localized month and day names. Usable in Node.js or in the browser.

Installation

Install via npm:

% npm install date-names

Usage

The default locale is en (English). Thus, a require('date-names') implicitly does require('date-names/en').

var names = require('date-names');

names.months              // => ['January', 'February', 'March', ...]
names.abbreviated_months  // => ['Jan', 'Feb', 'Mar', 'Apr', ...]

names.days                // => ['Sunday', 'Monday', 'Tuesday', ...]
names.abbreviated_days    // => ['Sun', 'Mon', 'Tue', 'Wed', ...]

names.am                  // => 'AM'
names.pm                  // => 'PM'

You can fetch a different translation by requiring a specific locale:

var names = require('date-names/de');

names.months              // => ['Januar', 'Februar', 'März', ...]
names.abbreviated_months  // => ['Jan', 'Feb', 'Mär', 'Apr', ...]

names.days                // => ['Sonntag', 'Montag', 'Dienstag', ...]
names.abbreviated_days    // => ['So', 'Mo', 'Di', 'Mi', ...]

names.am                  // => 'vormittags'
names.pm                  // => 'nachmittags'

English (en) and German (de) are currently the only supported locales. Pull requests welcome.

Contributing

Here's a quick guide:

  1. Fork the repo and make install.

  2. Run the tests. We only take pull requests with passing tests, and it's great to know that you have a clean slate: make test.

  3. Add a test for your change. Only refactoring and documentation changes require no new tests. If you are adding functionality or are fixing a bug, we need a test!

  4. Make the test pass.

  5. Push to your fork and submit a pull request.

Licence

Released under The MIT License.