chai 1.8.1 → 1.10.0

package/.npmignore

@@ -6,7 +6,7 @@ component.json
 components/
 build/
 lib-cov/
-coverage.html
+coverage/
 .travis.yml
 .mailmap
 Makefile

package/CONTRIBUTING.md

@@ -0,0 +1,173 @@
+# Chai Contribution Guidelines
+
+We like to encourage you to contribute to the Chai.js repository. This should be as easy as possible for you but there are a few things to consider when contributing. The following guidelines for contribution should be followed if you want to submit a pull request or open an issue.
+
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
+
+#### Table of Contents
+
+- [TLDR;](#tldr)
+- [Contributing](#contributing)
+  - [Bug Reports](#bugs)
+  - [Feature Requests](#features)
+  - [Pull Requests](#pull-requests)
+- [Support](#support)
+  - [Resources](#resources)
+  - [Core Contributors](#contributors)
+
+<a name="tldr"></a>
+## TLDR;
+
+- Creating an Issue or Pull Request requires a [GitHub](http://github.com) account.
+- Issue reports should be **clear**, **concise** and **reproducible**. Check to see if your issue has already been resolved in the [master]() branch or already reported in Chai's [GitHub Issue Tracker](https://github.com/chaijs/chai/issues).
+- Pull Requests must adhere to strict [coding style guidelines](https://github.com/chaijs/chai/wiki/Chai-Coding-Style-Guide).
+- In general, avoid submitting PRs for new Assertions without asking core contributors first. More than likely it would be better implemented as a plugin.
+- Additional support is available via the [Google Group](http://groups.google.com/group/chaijs) or on irc.freenode.net#chaijs.
+- **IMPORTANT**: By submitting a patch, you agree to allow the project owner to license your work under the same license as that used by the project.
+
+
+
+<a name="contributing"></a>
+## Contributing
+
+The issue tracker is the preferred channel for [bug reports](#bugs),
+[feature requests](#features) and [submitting pull
+requests](#pull-requests), but please respect the following restrictions:
+
+* Please **do not** use the issue tracker for personal support requests (use
+  [Google Group](https://groups.google.com/forum/#!forum/chaijs) or IRC).
+* Please **do not** derail or troll issues. Keep the discussion on topic and
+  respect the opinions of others
+
+<a name="bugs"></a>
+### Bug Reports
+
+A bug is a **demonstrable problem** that is caused by the code in the repository.
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** &mdash; check if the issue has already been reported.
+2. **Check if the issue has been fixed** &mdash; try to reproduce it using the latest `master` or development branch in the repository.
+3. **Isolate the problem** &mdash; create a test case to demonstrate your issue. Provide either a repo, gist, or code sample to demonstrate you problem.
+
+A good bug report shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and/or Node.js versions experience the problem? What would you expect to be the outcome? All these details will help people to fix any potential bugs.
+
+Example:
+
+> Short and descriptive example bug report title
+>
+> A summary of the issue and the browser/OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.
+>
+> 1. This is the first step
+> 2. This is the second step
+> 3. Further steps, etc.
+>
+> `<url>` - a link to the reduced test case OR
+> ```js
+> expect(a).to.equal('a');
+> // code sample
+> ```
+>
+> Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).
+
+<a name="features"></a>
+### Feature Requests
+
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project. It's up to *you* to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
+
+Furthermore, since Chai.js has a [robust plugin API](http://chaijs.com/guide/plugins/), we encourage you to publish **new Assertions** as plugins. If your feature is an enhancement to an **existing Assertion**, please propose your changes as an issue prior to opening a pull request. If the core Chai.js contributors feel your plugin would be better suited as a core assertion, they will invite you to open a PR in [chaijs/chai](https://github.com/chaijs/chai).
+
+<a name="pull-requests"></a>
+### Pull Requests
+
+- PRs for new core-assertions are advised against.
+- PRs for core-assertion bug fixes are always welcome.
+- PRs for enhancing the interfaces are always welcome.
+- PRs that increase test coverage are always welcome.
+- PRs are scrutinized for coding-style.
+
+Good pull requests - patches, improvements, new features - are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
+
+**Please ask first** before embarking on any significant pull request (e.g. implementing features, refactoring code), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
+
+Please adhere to the coding conventions used throughout a project (indentation, accurate comments, etc.) and any other requirements (such as test coverage). Please review the [Chai.js Coding Style Guide](https://github.com/chaijs/chai/wiki/Chai-Coding-Style-Guide).
+
+Follow this process if you'd like your work considered for inclusion in the project:
+
+1. [Fork](http://help.github.com/fork-a-repo/) the project, clone your fork, and configure the remotes:
+
+```bash
+# Clone your fork of the repo into the current directory
+git clone https://github.com/<your-username>/<repo-name>
+# Navigate to the newly cloned directory
+cd <repo-name>
+# Assign the original repo to a remote called "upstream"
+git remote add upstream https://github.com/<upstream-owner>/<repo-name>
+```
+
+2. If you cloned a while ago, get the latest changes from upstream:
+
+```bash
+git checkout <dev-branch>
+git pull upstream <dev-branch>
+```
+
+3. Create a new topic branch (off the main project development branch) to contain your feature, change, or fix:
+
+```bash
+git checkout -b <topic-branch-name>
+```
+
+4. Commit your changes in logical chunks. Use Git's [interactive rebase](https://help.github.com/articles/interactive-rebase) feature to tidy up your commits before making them public.
+
+5. Locally merge (or rebase) the upstream development branch into your topic branch:
+
+```bash
+git pull [--rebase] upstream <dev-branch>
+```
+
+6. Push your topic branch up to your fork:
+
+```bash
+git push origin <topic-branch-name>
+```
+
+7. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description.
+
+**IMPORTANT**: By submitting a patch, you agree to allow the project owner to license your work under the same license as that used by the project.
+
+<a name="support"></a>
+## Support
+
+<a name="resources"></a>
+### Resources
+
+For most of the documentation you are going to want to visit [ChaiJS.com](http://chaijs.com).
+
+- [Getting Started Guide](http://chaijs.com/guide/)
+- [API Reference](http://chaijs.com/api/)
+- [Plugins](http://chaijs.com/plugins/)
+
+Alternatively, the [wiki](https://github.com/chaijs/chai/wiki) might be what you are looking for.
+
+- [Chai Coding Style Guide](https://github.com/chaijs/chai/wiki/Chai-Coding-Style-Guide)
+- [Third-party Resources](https://github.com/chaijs/chai/wiki/Third-Party-Resources)
+
+Or finally, you may find a core-contributor or like-minded developer in any of our support channels.
+
+- IRC: irc.freenode.org #chaijs
+- [Mailing List / Google Group](https://groups.google.com/forum/#!forum/chaijs)
+
+<a name="contributors"></a>
+### Core Contributors
+
+Feel free to reach out to any of the core-contributors with you questions or concerns. We will do our best to respond in a timely manner.
+
+- Jake Luer
+  - GH: [@logicalparadox](https://github.com/logicalparadox)
+  - TW: [@jakeluer](http://twitter.com/jakeluer)
+  - IRC: logicalparadox
+- Veselin Todorov
+  - GH: [@vesln](https://github.com/vesln/)
+  - TW: [@vesln](http://twitter.com/vesln)
+  - IRC: vesln

package/History.md

@@ -1,4 +1,112 @@
 
+1.10.0 / 2014-11-10 
+==================
+
+ * Merge pull request #297 from prodatakey/noopchainfunc
+ * Merge pull request #300 from julienw/299-fix-getMessage-test
+ * Fix #299: the test is defining global variables
+ * Add a couple more unit tests
+ * Add unit tests for chained terminating property asserts
+ * Revise documentation wording
+ * Add docs for function style NOOP asserts
+ * Make the NOOP function a shared constant
+ * Merge pull request #298 from dasilvacontin/negativeZeroLogging
+ * why not more assertions
+ * added test for inspecting `-0`
+ * a more readable/simple condition statement, as pointed out by @keithamus
+ * added check for logging negative zero
+ * Change test to not trigger argument bug
+ * Allows writing lint-friendly tests
+ * readme: update contributors for 1.9.2
+
+1.9.2 / 2014-09-29 
+==================
+
+ * Merge pull request #268 from charlierudolph/cr-lazyMessages
+ * Merge pull request #269 from charlierudolph/cr-codeCleanup
+ * Merge pull request #277 from charlierudolph/fix-doc
+ * Merge pull request #279 from mohayonao/fix-closeTo
+ * Merge pull request #292 from boneskull/mocha
+ * resolves #255: upgrade mocha
+ * Merge pull request #289 from charlierudolph/cr-dryUpCode
+ * Dry up code
+ * Merge pull request #275 from DrRataplan/master
+ * assert: .closeTo() verify value's type before assertion
+ * Rewrite pretty-printing HTML elements to prevent throwing internal errors Fixes errors occuring when using a non-native DOM implementation
+ * Fix assert documentation
+ * Remove unused argument
+ * Allow messages to be functions
+ * Merge pull request #267 from shinnn/master
+ * Use SVG badge
+ * Merge pull request #264 from cjthompson/keys_diff
+ * Show diff for keys assertion
+
+1.9.1 / 2014-03-19 
+==================
+
+  * deps update
+  * util: [getActual] select actual logic now allows undefined for actual. Closes #183
+  * docs: [config] make public, express param type
+  * Merge pull request #251 from romario333/threshold3
+  * Fix issue #166 - configurable threshold in objDisplay.
+  * Move configuration options to config.js.
+  * Merge pull request #233 from Empeeric/master
+  * Merge pull request #244 from leider/fix_for_contains
+  * Merge pull request #247 from didoarellano/typo-fixes
+  * Fix typos
+  * Merge pull request #245 from lfac-pt/patch-1
+  * Update `exports.version` to 1.9.0
+  * aborting loop on finding
+  * declaring variable only once
+  * additional test finds incomplete implementation
+  * simplified code
+  * fixing #239 (without changing chai.js)
+  * ssfi as it should be
+  * Merge pull request #228 from duncanbeevers/deep_members
+  * Deep equality check for collection membership
+
+1.9.0 / 2014-01-29 
+==================
+
+  * docs: add contributing.md #238
+  * assert: .throws() returns thrown error. Closes #185
+  * Merge pull request #232 from laconbass/assert-throws
+  * assert: .fail() parameter mismatch. Closes #206
+  * Merge branch 'karma-fixes'
+  * Add karma phantomjs launcher
+  * Use latest karma and sauce launcher
+  * Karma tweaks
+  * Merge pull request #230 from jkroso/include
+  * Merge pull request #237 from chaijs/coverage
+  * Add coverage to npmignore
+  * Remove lib-cov from test-travisci dependents
+  * Remove the not longer needed lcov reporter
+  * Test coverage with istanbul
+  * Remove jscoverage
+  * Remove coveralls
+  * Merge pull request #226 from duncanbeevers/add_has
+  * Avoid error instantiation if possible on assert.throws
+  * Merge pull request #231 from duncanbeevers/update_copyright_year
+  * Update Copyright notices to 2014
+  * handle negation correctly
+  * add failing test case
+  * support `{a:1,b:2}.should.include({a:1})`
+  * Merge pull request #224 from vbardales/master
+  * Add `has` to language chains
+  * Merge pull request #219 from demands/overwrite_chainable
+  * return error on throw method to chain on error properties, possibly different from message
+  * util: store chainable behavior in a __methods object on ctx
+  * util: code style fix
+  * util: add overwriteChainableMethod utility (for #215)
+  * Merge pull request #217 from demands/test_cleanup
+  * test: make it possible to run utilities tests with --watch
+  * makefile: change location of karma-runner bin script
+  * Merge pull request #202 from andreineculau/patch-2
+  * test: add tests for throwing custom errors
+  * Merge pull request #201 from andreineculau/patch-1
+  * test: updated for the new assertion errors
+  * core: improve message for assertion errors (throw assertion)
+
 1.8.1 / 2013-10-10 
 ==================
 

package/README.md

@@ -5,60 +5,90 @@ can be delightfully paired with any javascript testing framework.
 
 For more information or to download plugins, view the [documentation](http://chaijs.com).
 
-[![Build Status](https://travis-ci.org/chaijs/chai.png?branch=master)](https://travis-ci.org/chaijs/chai) [![Coverage Status](https://coveralls.io/repos/chaijs/chai/badge.png?branch=master)](https://coveralls.io/r/chaijs/chai?branch=master)
+[![Build Status](https://travis-ci.org/chaijs/chai.svg?branch=master)](https://travis-ci.org/chaijs/chai)
 
 [![Selenium Test Status](https://saucelabs.com/browser-matrix/chaijs.svg)](https://saucelabs.com/u/chaijs)
 
+### Plugins
+
+Chai offers a robust Plugin architecture for extending Chai's assertions and interfaces.
+
+- Need a plugin? View the [official plugin list](http://chaijs.com/plugins).
+- Have a plugin and want it listed? Open a Pull Request at [chaijs/chai-docs:plugin.js](https://github.com/chaijs/chai-docs/blob/master/plugins.js#L1-L12). 
+- Want to build a plugin? Read the [plugin api documentation](http://chaijs.com/guide/plugins/).
+
 ### Related Projects
 
 - [chaijs / assertion-error](https://github.com/chaijs/assertion-error): Custom `Error` constructor thrown upon an assertion failing.
-- [chaijs / deep-eql](https://github.com/chaijs/deep-eql): Improved deep equality testing for Node.js and the browser. 
+- [chaijs / deep-eql](https://github.com/chaijs/deep-eql): Improved deep equality testing for Node.js and the browser.
 
 ### Contributors
 
-       project  : chai
-       repo age : 1 year, 9 months
-       active   : 139 days
-       commits  : 693
-       files    : 54
-       authors  :
-         518  Jake Luer               74.7%
-          66  Veselin Todorov         9.5%
-          43  Domenic Denicola        6.2%
-           6  Ruben Verborgh          0.9%
-           5  George Kats             0.7%
-           5  Jo Liss                 0.7%
-           5  Juliusz Gonera          0.7%
-           5  Scott Nonnenberg        0.7%
-           4  John Firebaugh          0.6%
-           4  Nick Heiner             0.6%
-           4  josher19                0.6%
-           3  Jeff Barczewski         0.4%
-           3  Ryunosuke SATO          0.4%
-           2  Bartvds                 0.3%
-           2  Edwin Shao              0.3%
-           2  Jakub Nešetřil          0.3%
-           2  Teddy Cross             0.3%
-           1  Anand Patil             0.1%
-           1  Benjamin Horsleben      0.1%
-           1  Brandon Payton          0.1%
-           1  Chris Connelly          0.1%
-           1  Chun-Yi                 0.1%
-           1  DD                      0.1%
-           1  Jeff Welch              0.1%
-           1  Kilian Ciuffolo         0.1%
-           1  Niklas Närhinen         0.1%
-           1  Paul Miller             0.1%
-           1  Sasha Koss              0.1%
-           1  Victor Costan           0.1%
-           1  Vinay Pulim             0.1%
-           1  piecioshka              0.1%
+     repo age : 2 years, 11 months
+     active   : 189 days
+     commits  : 792
+     files    : 57
+     authors  :
+       551  Jake Luer               69.6%
+        79  Veselin Todorov         10.0%
+        43  Domenic Denicola        5.4%
+         7  Joshua Perry            0.9%
+         6  Ruben Verborgh          0.8%
+         5  George Kats             0.6%
+         5  Jo Liss                 0.6%
+         5  Juliusz Gonera          0.6%
+         5  Scott Nonnenberg        0.6%
+         5  leider                  0.6%
+         4  David da Silva          0.5%
+         4  John Firebaugh          0.5%
+         4  Max Edmands             0.5%
+         4  Nick Heiner             0.5%
+         4  Veselin                 0.5%
+         4  charlierudolph          0.5%
+         4  josher19                0.5%
+         3  Andrei Neculau          0.4%
+         3  Duncan Beevers          0.4%
+         3  Jake Rosoman            0.4%
+         3  Jeff Barczewski         0.4%
+         3  Keith Cirkel            0.4%
+         3  Ryunosuke SATO          0.4%
+         2  Bartvds                 0.3%
+         2  Edwin Shao              0.3%
+         2  Jakub Nešetřil          0.3%
+         2  Roman Masek             0.3%
+         2  Teddy Cross             0.3%
+         1  Anand Patil             0.1%
+         1  Benjamin Horsleben      0.1%
+         1  Brandon Payton          0.1%
+         1  Chris Connelly          0.1%
+         1  Chris Thompson          0.1%
+         1  Christopher Hiller      0.1%
+         1  Chun-Yi                 0.1%
+         1  DD                      0.1%
+         1  Dido Arellano           0.1%
+         1  Jeff Welch              0.1%
+         1  Julien Wajsberg         0.1%
+         1  Kilian Ciuffolo         0.1%
+         1  Luís Cardoso            0.1%
+         1  Martin Middel           0.1%
+         1  Niklas Närhinen         0.1%
+         1  Paul Miller             0.1%
+         1  Refael Ackermann        0.1%
+         1  Sasha Koss              0.1%
+         1  Victor Costan           0.1%
+         1  Vinay Pulim             0.1%
+         1  Virginie BARDALES       0.1%
+         1  laconbass               0.1%
+         1  mohayonao               0.1%
+         1  piecioshka              0.1%
+         1  shinnn                  0.1%
+
 
 ## License
 
 (The MIT License)
 
-Copyright (c) 2011-2013 Jake Luer <jake@alogicalparadox.com>
+Copyright (c) 2011-2014 Jake Luer <jake@alogicalparadox.com>
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/ReleaseNotes.md

@@ -1,5 +1,225 @@
 # Release Notes
 
+## 1.10.0 / 2014-11-10 
+
+The following changes are required if you are upgrading from the previous version:
+
+- **Users:**
+  - No changes required
+- **Plugin Developers:** 
+  - Review `addChainableNoop` notes below.
+- **Core Contributors:** 
+  - Refresh `node_modules` folder for updated dependencies. 
+
+### Noop Function for Terminating Assertion Properties
+
+The following assertions can now also be used in the function-call form:
+
+* ok
+* true
+* false
+* null
+* undefined
+* exist
+* empty
+* arguments
+* Arguments
+
+The above list of assertions are property getters that assert immediately on 
+access. Because of that, they were written to be used by terminating the assertion 
+chain with a property access.
+
+```js
+expect(true).to.be.true;
+foo.should.be.ok;
+```
+
+This syntax is definitely aesthetically pleasing but, if you are linting your 
+test code, your linter will complain with an error something like "Expected an 
+assignment or function call and instead saw an expression." Since the linter 
+doesn't know about the property getter it assumes this line has no side-effects, 
+and throws a warning in case you made a mistake.
+
+Squelching these errors is not a good solution as test code is getting to be 
+just as important as, if not more than, production code. Catching syntactical 
+errors in tests using static analysis is a great tool to help make sure that your 
+tests are well-defined and free of typos.
+
+A better option was to provide a function-call form for these assertions so that 
+the code's intent is more clear and the linters stop complaining about something 
+looking off. This form is added in addition to the existing property access form 
+and does not impact existing test code.
+
+```js
+expect(true).to.be.true();
+foo.should.be.ok();
+```
+
+These forms can also be mixed in any way, these are all functionally identical:
+
+```js
+expect(true).to.be.true.and.not.false();
+expect(true).to.be.true().and.not.false;
+expect(true).to.be.true.and.not.false;
+```
+
+#### Plugin Authors
+
+If you would like to provide this function-call form for your terminating assertion 
+properties, there is a new function to register these types of asserts. Instead 
+of using `addProperty` to register terminating assertions, simply use `addChainableNoop` 
+instead; the arguments to both are identical. The latter will make the assertion 
+available in both the attribute and function-call forms and should have no impact 
+on existing users of your plugin.
+
+### Community Contributions
+
+- [#297](https://github.com/chaijs/chai/pull/297) Allow writing lint-friendly tests. [@joshperry](https://github.com/joshperry)
+- [#298](https://github.com/chaijs/chai/pull/298) Add check for logging `-0`. [@dasilvacontin](https://github.com/dasilvacontin)
+- [#300](https://github.com/chaijs/chai/pull/300) Fix #299: the test is defining global variables [@julienw](https://github.com/julienw)
+
+Thank you to all who took time to contribute!
+
+## 1.9.2 / 2014-09-29 
+
+The following changes are required if you are upgrading from the previous version:
+
+- **Users:**
+  - No changes required
+- **Plugin Developers:** 
+  - No changes required
+- **Core Contributors:** 
+  - Refresh `node_modules` folder for updated dependencies. 
+
+### Community Contributions
+
+- [#264](https://github.com/chaijs/chai/pull/264) Show diff for keys assertions [@cjthompson](https://github.com/cjthompson)
+- [#267](https://github.com/chaijs/chai/pull/267) Use SVG badges [@shinnn](https://github.com/shinnn)
+- [#268](https://github.com/chaijs/chai/pull/268) Allow messages to be functions (sinon-compat) [@charlierudolph](https://github.com/charlierudolph)
+- [#269](https://github.com/chaijs/chai/pull/269) Remove unused argument for #lengthOf [@charlierudolph](https://github.com/charlierudolph)
+- [#275](https://github.com/chaijs/chai/pull/275) Rewrite pretty-printing HTML elements to prevent throwing internal errors [@DrRataplan](https://github.com/DrRataplan)
+- [#277](https://github.com/chaijs/chai/pull/277) Fix assert documentation for #sameMembers [@charlierudolph](https://github.com/charlierudolph)
+- [#279](https://github.com/chaijs/chai/pull/279) closeTo should check value's type before assertion [@mohayonao](https://github.com/mohayonao)
+- [#289](https://github.com/chaijs/chai/pull/289) satisfy is called twice [@charlierudolph](https://github.com/charlierudolph)
+- [#292](https://github.com/chaijs/chai/pull/292) resolve conflicts with node-webkit and global usage [@boneskull](https://github.com/boneskull)
+
+Thank you to all who took time to contribute!
+
+## 1.9.1 / 2014-03-19 
+
+The following changes are required if you are upgrading from the previous version:
+
+- **Users:**
+  - Migrate configuration options to new interface. (see notes)
+- **Plugin Developers:** 
+  - No changes required
+- **Core Contributors:** 
+  - Refresh `node_modules` folder for updated dependencies. 
+
+### Configuration
+
+There have been requests for changes and additions to the configuration mechanisms
+and their impact in the Chai architecture. As such, we have decoupled the 
+configuration from the `Assertion` constructor. This not only allows for centralized
+configuration, but will allow us to shift the responsibility from the `Assertion` 
+constructor to the `assert` interface in future releases.
+
+These changes have been implemented in a non-breaking way, but a depretiation
+warning will be presented to users until they migrate. The old config method will 
+be removed in either `v1.11.0` or `v2.0.0`, whichever comes first.
+
+#### Quick Migration
+
+```js
+// change this:
+chai.Assertion.includeStack = true;
+chai.Assertion.showDiff = false;
+
+// ... to this:
+chai.config.includeStack = true;
+chai.config.showDiff = false;
+```
+
+#### All Config Options
+
+##### config.includeStack
+
+- **@param** _{Boolean}_
+- **@default** `false`
+
+User configurable property, influences whether stack trace is included in 
+Assertion error message. Default of `false` suppresses stack trace in the error 
+message.
+
+##### config.showDiff
+
+- **@param** _{Boolean}_
+- **@default** `true`
+
+User configurable property, influences whether or not the `showDiff` flag 
+should be included in the thrown AssertionErrors. `false` will always be `false`; 
+`true` will be true when the assertion has requested a diff be shown.
+
+##### config.truncateThreshold **(NEW)**
+
+- **@param** _{Number}_
+- **@default** `40`
+
+User configurable property, sets length threshold for actual and expected values 
+in assertion errors. If this threshold is exceeded, the value is truncated.
+
+Set it to zero if you want to disable truncating altogether.
+
+```js
+chai.config.truncateThreshold = 0; // disable truncating
+```
+
+### Community Contributions
+
+- [#228](https://github.com/chaijs/chai/pull/228) Deep equality check for memebers. [@duncanbeevers](https://github.com/duncanbeevers)
+- [#247](https://github.com/chaijs/chai/pull/247) Proofreading. [@didorellano](https://github.com/didoarellano)
+- [#244](https://github.com/chaijs/chai/pull/244) Fix `contain`/`include` 1.9.0 regression. [@leider](https://github.com/leider)
+- [#233](https://github.com/chaijs/chai/pull/233) Improvements to `ssfi` for `assert` interface. [@refack](https://github.com/refack)
+- [#251](https://github.com/chaijs/chai/pull/251) New config option: object display threshold. [@romario333](https://github.com/romario333)
+
+Thank you to all who took time to contribute!
+
+### Other Bug Fixes
+
+- [#183](https://github.com/chaijs/chai/issues/183) Allow `undefined` for actual. (internal api)
+- Update Karam(+plugins)/Istanbul to most recent versions.
+
+## 1.9.0 / 2014-01-29 
+
+The following changes are required if you are upgrading from the previous version:
+
+- **Users:**
+  - No changes required
+- **Plugin Developers:** 
+  - Review [#219](https://github.com/chaijs/chai/pull/219).
+- **Core Contributors:** 
+  - Refresh `node_modules` folder for updated dependencies. 
+
+### Community Contributions
+
+- [#202](https://github.com/chaijs/chai/pull/201) Improve error message for .throw(). [@andreineculau](https://github.com/andreineculau)
+- [#217](https://github.com/chaijs/chai/pull/217) Chai tests can be run with `--watch`. [@demands](https://github.com/demands)
+- [#219](https://github.com/chaijs/chai/pull/219) Add overwriteChainableMethod utility. [@demands](https://github.com/demands)
+- [#224](https://github.com/chaijs/chai/pull/224) Return error on throw method to chain on error properties. [@vbardales](https://github.com/vbardales)
+- [#226](https://github.com/chaijs/chai/pull/226) Add `has` to language chains. [@duncanbeevers](https://github.com/duncanbeevers)
+- [#230](https://github.com/chaijs/chai/pull/230) Support `{a:1,b:2}.should.include({a:1})` [@jkroso](https://github.com/jkroso)
+- [#231](https://github.com/chaijs/chai/pull/231) Update Copyright notices to 2014 [@duncanbeevers](https://github.com/duncanbeevers)
+- [#232](https://github.com/chaijs/chai/pull/232) Avoid error instantiation if possible on assert.throws. [@laconbass](https://github.com/laconbass)
+
+Thank you to all who took time to contribute!
+
+### Other Bug Fixes
+
+- [#225](https://github.com/chaijs/chai/pull/225) Improved AMD wrapper provided by upstream `component(1)`.
+- [#185](https://github.com/chaijs/chai/issues/185) `assert.throws()` returns thrown error for further assertions.
+- [#237](https://github.com/chaijs/chai/pull/237) Remove coveralls/jscoverage, include istanbul coverage report in travis test.
+- Update Karma and Sauce runner versions for consistent CI results. No more karma@canary.
+
 ## 1.8.1 / 2013-10-10 
 
 The following changes are required if you are upgrading from the previous version:

package/bower.json

@@ -1,6 +1,6 @@
 {
     "name": "chai"
-  , "version": "1.8.1"
+  , "version": "1.10.0"
   , "description": "BDD/TDD assertion library for node.js and the browser. Test framework agnostic."
   , "license": "MIT"
   , "keywords": [