* Update benchmarking diagram with latest stats
* Use a higher res png and include versions
* Export to PDF → convert to PNG for higher res chart
* Improve color contrast
* Some micro-ops index.js
* Update modification notes
* Get rid of strict
* Update numbers
* Update changelog
* ignore VS Code config
Co-authored-by: Chris Bolin, Phil Plückthun
- Update library to include ES.next support for `Map`, `Set`, `ArrayBuffer`. Part of #36
- Update to `fast-deep-equal@3.1.1` with modified support for ES.next data types.
- Upgrade lots of `devDependenices`
- Use `fast-deep-equal` tests directly in our correctness tests.
- Update CI to modern Node.js versions.
- **Note**: There's a bug / limitation of `Set` comparisons whereby objects are compared by reference not value. Tracked at #50 . In our `yarn benchmark`, `lodash.isEqual` gets test differences because it correctly handles those.
@chrisbolin we're adding maintenance status to all our OSS. I think `react-fast-compare` should probably be listed as "Active". I also considered "Stable". If you think that's more appropriate, please replace my note with:
```
Maintenance Status: Stable
Formidable is not planning to develop any new features for this project. We are still responding to bug reports and security concerns. We are still welcoming PRs for this project, but PRs that include new features should be small and easy to integrate and should not include breaking changes.
```
Let me know if you have any questions
- Refactor the test directory structure.
- Imports the `node` tests into the browser, building with webpack. They are the source of truth.
- Run headless chrome in Travis.
- Run IE9 in Appveyor.
- Use `builder` to parallelize running lint and various tests.
- Fixes#7
* react-fast-compare README
* react-fast-compare package.json
* clear out bad fast-deep-equal references
* deeply test react elements, just not the _owner field; update tests
