eb50266b3a
With this change we update various browserslist configuration file to match newly generated projects. https://github.com/angular/angular-cli/blob/master/packages/schematics/angular/application/files/.browserslistrc.template PR Close #43417 |
||
|---|---|---|
| .. | ||
| e2e | ||
| src | ||
| .browserslistrc | ||
| .editorconfig | ||
| .gitignore | ||
| angular.json | ||
| karma.conf.js | ||
| package.json | ||
| README.md | ||
| tsconfig.app.json | ||
| tsconfig.json | ||
| tsconfig.server.json | ||
| tsconfig.spec.json | ||
| tslint.json | ||
| yarn.lock | ||
CliElementsUniversal
This project tests the integration of Angular Elements (@angular/elements) with SSR (via @angular/platform-server).
The project was generated with Angular CLI version 11.1.4.
Support for Angular Elements was added with ng add @angular/elements and for SSR with ng generate app-shell.
What this project tests is that an app can be successfully SSR'd even when it uses @angular/elements, which relies on certain DOM built-ins being available as soon as it is imported.
This is tested by generating the app-shell (using ng run cli-elements-universal:app-shell:production) and then verifying that the index.html file was generated correctly.
(See, the test-ssr script in package.json.)
NOTE:
Currently, domino (the server-side DOM implementation used by @angular/platform-server) does not support Web Components, so the Custom Elements functionality does not work on the server.