In order to work around an Angular Bazel bug where genfiles aren't
properly picked up in the `ng_module` metadata bundler, we need to
check-in the example module into the source-file and use the
example-module as a real source instead of generating it dynamically
through a genfile. This allows us to temporarily fix the examples package
until the bug (https://github.com/angular/angular/issues/30259) is fixed.
Updates all Angular packages expect "@angular/compiler-cli" to
the latest beta version. This allows us to pick up recent Bazel fixes
which allow us to fully re-enable all e2e tests. Additionally we can
now update to the latest `rules_nodejs` version that switched from
`rollup` to `terser`.
Additionally since we updated `@angular/bazel@8.0.0-beta.6`, we
can take advantage of https://github.com/angular/angular/commit/105cfaf
and move forward with using the Bazel `ng_package` output for the NPM
release output.
Also removes unused source-map-support dependency. The NodeJS rule now transitively bring in the `source-map-support` dependency and therefore we don't need to add it to various Bazel targets.
Also specifying the `jasmine` attribute is currently not working as it breaks
the runfile dependency of `@npm//@bazel/jasmine`. `@bazel/jasmine`
transitively brings its own version of `jasmine`.
Explicitly passes required runfiles in nodejs_binary
Fixes#15614
This allows us to cherry-pick @kara's static query updates from the
`ivy-2019` branch.
This change includes:
* Adding missing dependencies for various Angular subpackages
* Add umd assets where they are now necessary
* Configure bazel to target ES5 output as a workaround for https://github.com/angular/angular/issues/29107
* Updates most npm dependencies to the @npm// workspace
* Updates general workspace setup, RBE config, ngcontainer
* Update to rxjs 6.4.0 (building from source no longer needed)
* Added rxjs_shims for ts_web_test and ts_devserver targets
* Removed index.bzl and angular_material_setup_workspace (not needed anymore since material won't be built from source)
* Use browser_repositories() from @npm_bazel_karma which have pinned browsers that work on all platforms
* Change dgeni processor functions from arrow function to `function` to
work around `@npm//di` not supporting arrow functions
Co-authored-by: Greg Magolan <gmagolan@gmail.com>
* In order to debug the example data for the tests on `material.angular.io`, I had to look into the `example-module.ts` output, but it was nearly impossible to read because we don't pretty print the auto-generated code.
In c64503e0bf the logic that outputs the list of components was reworked to use `JSON.stringify`. As a result, the data that is generated has the `component` inside quotes, rather than a reference to the component class itself. This breaks the demo app. The following changes add some extra logic to remove the quotes around the `component`.
Paul Gschwendtner