de8ebbdfd0
Currently, it's not possible to tree-shake away the coordination layer between HammerJS and Angular's EventManager. This means that you get the HammerJS support code in your production bundle whether or not you actually use the library. This commit removes the Hammer providers from the default platform_browser providers list and instead provides them as part of a `HammerModule`. Apps on Ivy just need to import the `HammerModule` at root to turn on Hammer support. Otherwise all Hammer code will tree-shake away. View Engine apps will require no change. BREAKING CHANGE Previously, in Ivy applications, Hammer providers were included by default. With this commit, apps that want Hammer support must import `HammerModule` in their root module. PR Close #32203 |
||
|---|---|---|
| .. | ||
| brotli-cli | ||
| build | ||
| cjs-jasmine | ||
| gulp-tasks | ||
| material-ci | ||
| ngcontainer | ||
| npm | ||
| public_api_guard | ||
| rxjs | ||
| size-tracking | ||
| source-map-test | ||
| symbol-extractor | ||
| testing | ||
| ts-api-guardian | ||
| tslint | ||
| validate-commit-message | ||
| yarn | ||
| BUILD.bazel | ||
| bazel_stamp_vars.js | ||
| check-environment.js | ||
| defaults.bzl | ||
| jasmine-seed-generator.js | ||
| jsconfig.json | ||
| postinstall-patches.js | ||
| rebase-pr.js | ||
| rollup_bundle_commonjs_ignoreGlobal.patch | ||
| tsconfig-test.json | ||
| tsconfig.json | ||
| types.d.ts | ||
| utils.inc | ||