angular-cn/integration/platform-server
George Kalpakas 4ece0eb27c build: use exact versions for integration project dependencies (#33968)
Since we cannot run `yarn install` with the `--frozen-lockfile` option
(because we want to be able to install the locally built Angular
packages), integration project lockfiles are susceptible to getting
out-of-sync with the corresponding `package.json`. When this happens,
yarn will install the latest available version that satisfies the
version range specified in `package.json`.

This commit adds another line of defense, by specifying exact versions
for the dependencies in `package.json` files (i.e. `1.33.7` instead of
`^1.33.0`). While transitive dependencies will be unpinned, this still
ensures that the same version of direct dependencies will be installed
in case of an out-of-sync lockfile, thus reducing the probability of
random failures.

PR Close #33968
2019-11-26 16:08:32 -08:00
..
e2e
src build: reference zone.js from source directly instead of npm. (#33046) 2019-11-06 00:48:34 +00:00
README.md
build.sh
package.json build: use exact versions for integration project dependencies (#33968) 2019-11-26 16:08:32 -08:00
tsconfig.json feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
webpack.client.config.js
webpack.server.config.js
yarn.lock build: use exact versions for integration project dependencies (#33968) 2019-11-26 16:08:32 -08:00

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