ember-sugar-date-shim

Purpose

Expose an ES6 module shim for the global Sugar instance's Date and all defined locales.

Installation

$ ember install ember-sugar-date-shim

Requirements

• Ember >= 1.13.0

Dependencies

• The latest release version of the sugar-date NPM package.

Tested Against

Usage

Import the Sugar global instance in your controller, route, or component js-file:

import Sugar from 'ember-sugar-date';

Then somewhere in your js-code, you can use the Sugar.Date object as you normally would. For example:

return Sugar.Date.full(new Date());

Sugar.js Dates Documentation

Sugar.js Dates

Collaboration Information

This README outlines the details of collaborating on this Ember add-on.

Installation

• git clone [email protected]:cybertoothca/ember-sugar-date-shim.git
• cd ember-sugar-date-shim

With NPM

npm install

With Yarn

yarn

Running

• ember serve
• Visit your app at http://localhost:4200.

Running Tests

• npm test (Runs ember try:each to test your add-on against multiple Ember versions)
• ember test
• ember test --server

Building

• ember build

For more information on using ember-cli, visit https://ember-cli.com.

Linking This Add-on For Local Testing

Linking

1. From the command line at the root of this project run the npm link command to link this add-on within your local node repository.
2. From the other Ember project that you wish to test this add-on in, execute the following command: npm link ember-sugar-date-shim.
3. Now in that same other Ember project, you should go into the package.json and add the ember add-on with the version *. It will look something like this: "ember-sugar-date-shim": "*". Now when/if you execute npm install on this other project it will know to look for the linked add-on rather than fetch it from the central repository.

Unlinking

1. Remove the add-on from your local node repository with the following command (that can be run anywhere): npm uninstall -g ember-sugar-date-shim
2. Remove the reference to the ember-sugar-date-shim in your other project's package.json.
3. Run an npm prune from the root of your other project's command line.