Date JS was started by Geoffrey McGill in 2007, he abandoned it on May 13th 2008; leaving the Google Code repository stagnant and with many bugs unresolved.
DateJS supports running either your regular web browser as a client library or Node.js.
Installation is as easy as running:
npm install datejs
If you use Bower to manage your frontend packages then it's also really simple:
bower install datejs
- For production environments include the production ready minified file from the Build directory on your page.
- For debugging (eg, in development) include the unminified and fully commented version
In Node.js you can just call
Date.i18n.setLanguage with the IETF appropriate code (e.g. "de-DE", or "es-MX") and DateJS will load the file automatically. For the browser DateJS has langauge support in one of two ways:
- Either download the appropriate file from the Build directory of your choice. Files are named after the IETF code the load (i.e.
date-es-MX.jsloads Mexican Spanish).
- Or set
Date.Config.i18nto the location of the internationalization files on your server and DateJS will dynamically load the files by script element insertion.
DateJS will always support loading US English via
Date.i18n.setLanguage("en-US") no matter what other language is specifically loaded. So you can always support both your localization and the English speaking world.
buildOutput from the Grunt powered build process
developmentNon-minified files with full comments. Suitable for development environments.
productionFully minified (by Google's Closure Compiler) files suitable for production.
srcAll the source files used to build the final files.
coreThe main DateJS source files.
i18nInternationalization files. Language specifics (days of the week, regex formats,etc). Organized by IETF language tag (eg - en-US, etc).
specsUnit Tests written using Jasmine. Code coverage is calculated by BlanketJS.
testsOrginal unit tests for 2008 project. Deprecated