583a9d38a1
Close #35157
In the current version of zone.js, zone.js uses it's own package format, and it is not following the rule
of Angualr package format(APF), so it is not easily to be consumed by Angular CLI or other bundle tools.
For example, zone.js npm package has two bundles,
1. zone.js/dist/zone.js, this is a `es5` bundle.
2. zone.js/dist/zone-evergreen.js, this is a `es2015` bundle.
And Angular CLI has to add some hard-coding code to handle this case, o
|
||
---|---|---|
.. | ||
e2e | ||
src | ||
README.md | ||
build.sh | ||
package.json | ||
tsconfig.json | ||
webpack.client.config.js | ||
webpack.server.config.js | ||
yarn.lock |
README.md
To add a new server side rendering E2E test
- Add a new server side rendered application to src/
- Edit webpack.client.config.js to add new entry point for the new client bundle
- The index.html can access the client bundle from /built/.js
- Edit src/server.ts to add the server side application to a new URL
- Add a protractor test in e2e/ to test with the new URL