* 2.5.0 changelog
* Update dependencies
* Colors are expected to be globals by the new AST test helpers
* Disable testing of deepStrictIncludeExpectedProperties in browsers for now
* Update output of compiler only
* Update browser compiler output
* Update docs output
* Document ast option
* Update output
* Fix and reenable deepStrict test for browser test suite
* Update output
* Build both a legacy and modern browser compiler
* Dynamic import example and documentation
* Update the docs to use the modern browser compiler if the browser supports it
* Update policy regarding Stage 3 features
* This never made sense, and assigning a string to index 0 *of a string* throws in Module mode (and silently does nothing in Script mode) so remove this unneeded code that throws when compiling `fn for i from from iterable` in Module mode
* Have browser-based tests use the ES module version if supported
* Simplify building logic
* Update output
* For the ES module version of the browser compiler, don't automatically attach the runScripts event handler
* Consistent comments
* Fix comment
* Explicitly turn off minify mangling, because it was previously implicitly disabled by the existence of the `eval` call we’re about to remove
* Update babel-core
* Run browser-compiled scripts using window.eval rather than just eval, to use a clean scope (many times faster)
* Update output
* Fix browser-based test broken by #5028
* Update output
* Bump version to 2.0.0; bump dependencies versions
* Make v2 docs the primary docs; jettison the v1 docs’ source: whenever the v1 docs need to be rebuild in the future, that can be done on the `1` branch and copied over; simplify folder tree
* Updated v1 docs that reflect that v2 is out and have updated paths to reflect that the v2 docs are now the primary docs, and the v1 docs only live under /v1/
* Add Google Analytics; track navigation, editing code and running code
* 2.0.0 changelog
* Fix link to root docs
* No more @next; installing local copy should be --save-dev
* Analytics on the browser-based tests page should prove fascinating . . .
* Update annotated source
* Add note to changelog clarifying scope
