Skip to content

Closure Rules v0.4.0

Compare
Choose a tag to compare
@jart jart released this 12 Nov 03:17
· 393 commits to master since this release

This release fixes bugs and upgrades certain dependencies. Migrating to this release should be relatively painless. The only breaking change you may encounter is that some linter warnings are now being treated as errors, which can be easily suppressed.

New Features

  • Closure Compiler conformance protobuf configuration files are now supported thanks to @hochhaus in 8fcdda1. Please note that In the near future, Closure Rules will open source Google's internal conformance configs and make them the default.

Bug Fixes

Breaking changes

  • All JsChecker warnings are now errors. If this breaks your build, please remember that the error message will contain a code you can add to the suppress attribute of closure_js_library to make it go away (if you'd prefer not to fix it.) We made this change because warnings are finicky; they don't show up when builds are cached, so they're sometimes hard to find again if they've already scrolled off the screen.
  • The incremental_dom library target was renamed @io_bazel_rules_closure//third_party/javascript/incremental_dom to improve compatibility with Google's internal repository in 1ddf26e

Upgrades

  • Closure Compiler v20160822 → v20161024 (Release notes)
    • Various compile time performance improvements to the optimization passes.
    • Better support/fixes for @abstract classes and methods
    • Polyfills for Promises.
    • Support for async/await by transpiling to generators.
  • Closure Library v20160822 → v20161024 (Release notes: v20160911, v20161024)
  • Closure Stylesheets 1.3.0 → 1.4.0 (Release notes)
    • Fixes nasty bug where compiler crashes for stylesheets with commas
  • Protobuf 3.0.0-beta-3 → 3.1.0