-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work with latest closure compiler #30
Comments
@ChadKillingsworth do you happen to know what the breaking change was? Seems like some default externs have moved or been removed? |
No not at all - but this is the second report I've seen of something similar. |
@MatrixFrog - known issue? should I file it on the closure-compiler issue tracker? |
I haven't seen this before, yeah please file it. |
devversion
added a commit
to devversion/material2
that referenced
this issue
May 21, 2017
* Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer and UglifyJS due to some bigger breaking changes * Skipped upgrading google-closure-compiler due to alexeagle/closure-compiler-angular-bundling#30
devversion
added a commit
to devversion/material2
that referenced
this issue
May 21, 2017
* Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to alexeagle/closure-compiler-angular-bundling#30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See angular/protractor#4176)
devversion
added a commit
to devversion/material2
that referenced
this issue
May 21, 2017
* Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to alexeagle/closure-compiler-angular-bundling#30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See angular/protractor#4176)
devversion
added a commit
to devversion/material2
that referenced
this issue
May 22, 2017
* Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to alexeagle/closure-compiler-angular-bundling#30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See angular/protractor#4176)
tinayuangao
pushed a commit
to angular/components
that referenced
this issue
May 22, 2017
* build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to alexeagle/closure-compiler-angular-bundling#30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See angular/protractor#4176) * Lock jasmine types
Moving issues from this repo to angular/closure-demo |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrading from v20170409 to v20170423 breaks the Angular example:
Release notes: https://github.com/google/closure-compiler/wiki/Releases#april-23-2017-v20170423
Broken build:
https://circleci.com/gh/alexeagle/closure-compiler-angular-bundling/82
cc @StephenFluin
The text was updated successfully, but these errors were encountered: