angular/integration/cli-elements-universal
Alan Agius 612eaca3c5 build: update cross-repo dependencies to latest stable version (#48216)
With this change we update the cross-repo dependencies to the latest stable version

PR Close #48216
2022-11-29 12:29:46 -08:00
..
e2e test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00
src build: update Angular tooling packages to 15.0.0-next.3 (#47584) 2022-09-30 10:53:04 -07:00
.editorconfig
.gitignore
angular.json test: remove defaultProject workspace option (#45410) 2022-03-24 10:49:57 -07:00
BUILD.bazel build: setup test targets for integration tests with new rule (#44238) 2021-12-08 13:42:41 -05:00
karma.conf.js test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238) 2021-12-08 13:42:42 -05:00
package.json test: replace --prod with --configuration production (#46548) 2022-06-28 09:39:05 -07:00
README.md
tsconfig.app.json
tsconfig.json
tsconfig.server.json
tsconfig.spec.json
tslint.json

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.