Want to see pretty graphs? Log in now!
npm install sugar
|356||downloads in the last day|
|2 288||downloads in the last week|
|9 559||downloads in the last month|
|Last Published By|
|Version||1.4.1 last updated 7 months ago|
|Keywords||functional, utility, ender|
spidex, nvi, node-document-differ, meteor-package-loader, node-document-storage-leveldb, flowambassador, bugsnag-notification-plugins, node-document-storage-fs, ccache, recliner, stone, cabrel-cfts-sanitize, node-document-serializer-json, grunt-missing-i18n, easy-mincer, grunt-contrib-ftpush, node-document, grunt-zuckrig-closure, sentence-tokenizer, nodize,
and 98 more
|Starred by||dbrockman, fgribreau, parmentf, pid, vegera|
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
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 now allows custom builds that let you opt in or out packages. This can be done here.
Custom builds can also be created with
script/build_custom.rb. With ruby installed, simply call:
ruby script/build_custom.rb core array string
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, especially methods in
core.js, the extending methods of which are required.
Unit Tests Node
npm test command to run unit tests.
Sugar has the following localizations available:
- English (en)
- French (fr)
- German (de)
- Spanish (es)
- Italian (it)
- Russian (ru)
- Finnish (fi)
- Swedish (sv)
- Danish (da)
- Dutch (nl)
- Polish (pl)
- Portuguese (pt)
- Korean (ko)
- Japanese (ja)
- 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:
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.
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. Not everything can be added to the main package, but I would like to have as many languages/formats as possible available. When adding a locale contribution, the most important thing is to add unit tests that assert the correct format. These unit tests are found at
test/environments/sugar/date_LOCALE.js. Simply add or adjust the formats for the locale (the more tests, the better!) and issue me a pull request -- I will update the code to add these locales/formats. Have a look at other unit tests files for an example of the unit testing format.
Contributing Lib Comparisons
Lib comparisons to various other libraries can be seen at http://sugarjs.com/libs. This is one of the areas where contributions are most welcome, as I don't have extensive knowledge of many different libraries, and there is much to cover. 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 I will push changes here out to the site every so often.
For other contributions, please add well formed unit tests in the Sugar environment at
test/environments/sugar/MODULE.js. 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
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.