b1fa1bf0d5
Rollup just prints a warning if an import cannot be resolved and ends up being treated as an external dependency. This in combination with the `silent = True` attribute for `rollup_bundle` means that bundles might end up being extremely small without people noticing that it misses actual imports. To improve this situation, the warning is replaced by an error if an import cannot be resolved. This unveiles an issue with the `ng_rollup_bundle` macro from dev-infra where imports in View Engine were not resolved but ended up being treated as external. This did not prevent benchmarks using this macro from working because the ConcatJS devserver had builtin resolution for workspace manifest paths. Though given the new check for no unresolved imports, this will now cause errors within Rollup, and we need to fix the resolution. We can fix the issue by temporarily enabling workspace linking. This does not have any performance downsides. To enable workspace linking (which we might need more often in the future given the linker taking over patched module resolution), we had to rename the `angular` dependency to a more specific one so that the Angular linker could link into `node_modules/angular`. PR Close #42760 |
||
|---|---|---|
| .. | ||
| common | ||
| compiler | ||
| core | ||
| forms | ||
| http | ||
| platform-browser | ||
| router/activated-route | ||
| service-worker | ||
| test-utils | ||
| testing | ||
| upgrade | ||
| BUILD.bazel | ||
| README.md | ||
| index.html | ||
| tsconfig-e2e.json | ||
README.md
API Examples
This folder contains small example apps that get in-lined into our API docs. Each example contains tests for application behavior (as opposed to testing Angular's behavior) just like an Angular application developer would write.
Running the examples
# Serving individual examples (e.g. common)
yarn bazel run //packages/examples/common:devserver
# "core" examples
yarn bazel run //packages/examples/core:devserver
Running the tests
yarn bazel test //packages/examples/...