build(docs-infra): update docs examples to latest v9#36015
build(docs-infra): update docs examples to latest v9#36015gkalpak wants to merge 23 commits intoangular:masterfrom
Conversation
|
|
|
You can preview db5524f at https://pr36015-db5524f.ngbuilds.io/. |
|
You can preview be3cbce at https://pr36015-be3cbce.ngbuilds.io/. |
be3cbce to
c6c456b
Compare
|
You can preview c6c456b at https://pr36015-c6c456b.ngbuilds.io/. |
petebacondarwin
left a comment
There was a problem hiding this comment.
LGTM:
I assume that the reason the commits are out of order in the GH UI is because of rebases holding on to old dates... This can be remedied with git rebase master --ignore-date but not important.
- commit 10/12 does a bit more than update the tsconfig.json - perhaps add some more explanation to the commit message?
- commit 12/12 !fixup seems like it should be its own commit with its own message, not a fixup...
IgorMinar
left a comment
There was a problem hiding this comment.
lgtm - global approval
but as discussed offline this is blocked until the next zone.js patch release is out.
Wow, thx, I didn't know
In each commit, I make the described change (e.g. update |
c6c456b to
b6843e7
Compare
|
You can preview b6843e7 at https://pr36015-b6843e7.ngbuilds.io/. |
…` docs examples (#36015) Previously, the `package.json` files added as boilerplate to docs example projects of type `systemjs` were incorrect/outdated. They contained unused dependencies and npm scripts and omitted used dependencies. This is not a big issue, because these examples are not offered as live StackBlitz examples or downloadable ZIP archives, but having incorrect `package.json` files is confusing and makes it more complicated to update these examples. This commit updates the `package.json` templates for the `systemjs` docs examples and other configuration files to include used dependencies (and remove unused ones). It also removes unused npm scripts. PR Close #36015
…ngularjs.org (#36015) In the example apps used in the `ngUpgrade` guide, the AngularJS files are loaded in `index.html` from `https://code.angularjs.org/`. Latest browsers prevent loading the scripts from a page running on localhost due to CORS: ``` Access to script at 'https://code.angularjs.org/1.5.5/angular.js' from origin 'http://localhost:9876' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. ``` NOTE: Loading the files from `code.angularjs.org` is not mentioned in the guide, therefore it is not needed to mention this config change there. PR Close #36015
…` docs examples (#36015) Previously, the `package.json` files added as boilerplate to docs example projects of type `systemjs` were incorrect/outdated. They contained unused dependencies and npm scripts and omitted used dependencies. This is not a big issue, because these examples are not offered as live StackBlitz examples or downloadable ZIP archives, but having incorrect `package.json` files is confusing and makes it more complicated to update these examples. This commit updates the `package.json` templates for the `systemjs` docs examples and other configuration files to include used dependencies (and remove unused ones). It also removes unused npm scripts. PR Close #36015
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This PR cleans-up the docs examples and updates them to v9 (and also updates the code to match what the latest CLI would generate for a new project).
This was originally part of #34374 (and split off for easier reviewing).
Partly addresses: FW-1609
Fixes #34382 and #34383.