mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00

Files

T

Andrew Scott 34b2d34d5b refactor(router): Remove RouterTestingModule in favor of RouterModule.forRoot (#49427 )

`RouterTestingModule` is not needed as of v16. Instead, TestBed
automatically provides `MockPlatformLocation` in order to help test
navigations in the application. The location mocks in the
RouterTestingModule aren't necessary anymore.

There doesn't appear to be any real documentation around
`RouterTestingModule` other than the API docs.

PR Close #49427

2023-04-04 15:12:33 -07:00

e2e

test: switch integration tests from puppeteer/webdriver-manager to Bazel-managed chromium (#44238 )

2021-12-08 13:42:42 -05:00

src

refactor(router): Remove RouterTestingModule in favor of RouterModule.forRoot (#49427 )

2023-04-04 15:12:33 -07:00

.editorconfig

…

.gitignore

…

angular.json

test: fix misconfiguration in tests (#49391 )

2023-03-15 16:59:50 -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

refactor: cleanup polyfills by importing zone.js directly in angular.json (#48380 )

2022-12-13 13:37:08 -08:00

tsconfig.json

…

tsconfig.server.json

…

tsconfig.spec.json

refactor: cleanup polyfills by importing zone.js directly in angular.json (#48380 )

2022-12-13 13:37:08 -08:00

tslint.json

…

README.md

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.