A Javascript library for working with native objects. http://sugarjs.com/
Pre-built scripts release/sugar.min.js and release/sugar.dev.js can be immediately included in any project. Both are the standard build of Sugar that includes default packages. release/sugar-full.min.js and release/sugar-full.dev.js include all packages. These pre-built scripts correspond to what is available on customize page on the main site.
In node, simply use npm install sugar for the full build.
If you are upgrading from an older version, please have a look at CAUTION.md which is a vetted changelog that details the severity of what has changed, and (sometimes) strategies for migrating. Going through this before you upgrade can make the process a lot less painful! Also please refer there for notes about a patch that applies to versions prior to v1.3.9.
Public stable releases will be made available on the site and also exist in release/.
Any push made to master branch should have its unit tests passing, although maybe not
in all browsing environments (IE, etc) to ensure that it is stable, at least to a certain degree.
Sugar allows custom builds that let you opt in or out packages. This can be done here.
Custom builds can also be created with script/create_build.rb. With ruby installed, simply call:
ruby script/create_build.rb --packages string,array
listing the packages you want to include. The advantage of using this script is that it will perform all the minification on the fly, providing more fine-grained control by allowing you to manipulate the source code in lib/ before building. If you want to remove specific methods from a package, you can do it this way. Be careful about removing dependencies however. Both lib/core/core.js and lib/common.js are required and will be added automatically. Be careful about removing methods in here as many methods are depended on by multiple packages.
Use the npm test command to run unit tests.
Sugar has the following localizations available:
- Danish (da)
- Dutch (nl)
- English (en)
- Finnish (fi)
- French (fr)
- German (de)
- Italian (it)
- Japanese (ja)
- Korean (ko)
- Polish (pl)
- Portuguese (pt)
- Russian (ru)
- Spanish (es)
- Swedish (sv)
- Simplified Chinese (zh-CN)
- Traditional Chinese (zh-TW)
These files can be added separately or built into the main package on the customize page. In addition to these major locales, custom locales can be added using:
Date.addLocale(LOCALE_CODE, LOCALIZATION_OBJECT)
Documentation for this available here. Also refer to lib/locales for examples of what kind of data and formats are required in localization objects. All localizations, including those not found in the main package will be kept here.
Dealing with timezones in Javascript can be tricky. Although timezones are outside the scope of Sugar, it does provide a hook that can allow timezone shifted dates to be used internally in place of normal ones. See the date reference for more.
If you do add a custom format for your locale, please consider forking and adding it to the repo! This especially includes the addition of new locales, but also new formats or tweaks to existing locales. When adding a locale contribution, the most important thing is to add unit tests that assert the correct format. These unit tests are found in test/environments/sugar/. Simply add or adjust the formats for the locale (the more tests, the better!) and issue me a pull request. Have a look at other unit tests files for an example of the unit testing format.
Lib comparisons to various other libraries can be seen at http://sugarjs.com/libs. To contribute simply find or create the appropriate lib name in docs/libs, and follow the format provided. This will be an ongoing process, and changes will be pushed out every so often.
For other contributions, please add well formed unit tests to test/environments/sugar/. Unit tests can be run directly in the browser from test/default.html, and should all be passing in all major browsers (Webkit,Mozilla,Opera, and IE6+). Node.js unit tests should also be passing and can be run in the console with npm test.
Also note that the source code is in the lib/ directory, and release is automatically built, so there is no need to changes files there.