Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
angular/aio/tools/examples/shared/package.json

89 lines
2.9 KiB
JSON
Raw Normal View History

feat(aio): copy example code from angular.io
2017-02-22 18:13:21 +00:00
{
"name": "angular-examples-master",
"version": "1.0.0",
"private": true,
"description": "Master package.json, the superset of all dependencies for all of the _example package.json files. See _boilerplate/package.json for example npm scripts.",
"scripts": {
"http-server": "http-server",
"protractor": "protractor",
build(docs-infra): use `puppeteer` to get a browser for docs examples tests (#35381) In #35049, integration and AIO tests were changed to use the browser provided by `puppeteer` in tests. This commit switches the docs examples tests to use the same setup. IMPLEMENTATION NOTE: The examples are used to create ZIP archives that docs users can download to experiment with. Since we want the downloaded projects to resemble an `@angular/cli` generated project, we do not want to affect the project's Protractor configuration in order to use `puppeteer`. To achieve this, a second Protractor configuration is created (which is ignored when creating the ZIP archives) that extends the original one and passes the approperiate arguments to use the browser provided by `puppeteer`. This new configuration (`protractor-puppeteer.conf.js`) is used when running the docs examples tests (on CI or locally during development). PR Close #35381
2020-02-13 14:58:04 +00:00
"webdriver:update": "node ../../../../scripts/webdriver-manager-update.js",
build(docs-infra): ensure all boilerplate dependencies are in sync (#47009) All docs examples share the same `node_modules/` (symlinked into each example from `aio/tools/examples/shared/node_modules/`). However, each example type has a different `package.json`, which comes from `aio/tools/examples/shared/boilerplate/*`). In order to ensure that the dependencies in each example's `package.json` are the same as the ones in the symlinked `node_modules/` (i.e. the ones that CI tests are run with), we have a script (`yarn run sync-deps`) that can sync dependencies from `shared/package.json` into the boilerplate `package.json` files. Previously, this script had to be run manually, which was easy to forget/not know about and resulted in the boilerplate dependencies often being out-of-sync with the ones in `shared/package.json` (and by extension, the ones that were actually installed in `node_modules/`). This commit helps keep the boilerplate dependencies up-to-date in the following ways: - Adds the `sync-deps` script to the `postinstall` scripts. This ensures that dependencies remain in sync whenever someone manually updates dependencies in `shared/package.json`. - Runs the `sync-deps` script as a Renovate post-upgrade task. This ensures that the depenencies remain in sync whenever Renovate updates dependencies in `shared/package.json`. For more info on configuring post-upgrade tasks in Renovate, see: - [postUpgradeTasks][1] - [allowedPostUpgradeCommands][2] - [allowPostUpgradeCommandTemplating][3] NOTE: For the Renovate change to take effect, the [global config][4] in `angular/dev-infra` also needs to be updated. This will be done in a separate PR. [1]: https://docs.renovatebot.com/configuration-options/#postupgradetasks [2]: https://docs.renovatebot.com/self-hosted-configuration/#allowedpostupgradecommands [3]: https://docs.renovatebot.com/self-hosted-configuration/#allowpostupgradecommandtemplating [4]: https://github.com/angular/dev-infra/blob/22d3067021130271afcfd02d063828c5bdd9c2d7/.github/ng-renovate/runner-config.js PR Close #47009
2022-08-02 07:21:48 +00:00
"postinstall": "yarn sync-deps && yarn webdriver:update",
build(docs-infra): simplify updating dependencies in docs examples boilerplate (#38992) Previously, when updating the dependency versions in `aio/tools/examples/shared/package.json` (which contains all dependencies used in docs examples projects), one had to manually go through all boilerplate directories and update the `package.json` files with the same versions. This commit simplifies this task by automating it via a Node.js script. PR Close #38992
2020-09-27 10:37:45 +00:00
"sync-deps": "node sync-boilerplate-dependencies"
feat(aio): copy example code from angular.io
2017-02-22 18:13:21 +00:00
},
build: set upper version limit for yarn to <2 (#34236) Rather than bumping up the allowed version of yarn on each release we should instead just allow for anything within the major version 1 range. PR Close #34236
2019-12-04 20:05:53 +00:00
"//engines-comment": "Keep this in sync with /package.json and /aio/package.json",
build: upgrade yarn to 1.3.2 (#21406) Fixes #20566 PR Close #21406
2018-01-09 10:02:03 +00:00
"engines": {
feat(core): drop support for Node.js 12 (#45286) Node.js v12 will become EOL on 2022-04-30. As a result, Angular CLI v14 will no longer support Node.js v12. BREAKING CHANGE: Support for Node.js v12 has been removed as it will become EOL on 2022-04-30. Please use Node.js v14.15 or later. PR Close #45286
2022-03-07 15:43:13 +00:00
"node": ">=14.0.0",
build: rely on engines to prevent using npm for dependency install (#41477) Rather than relying on a preinstall script, set `engine-strict` to `true` in a project `.npmrc` file, relying on the `engines` having `npm` set to note that yarn should be used instead. --- Output from `npm install` changes from: ``` $ npm install > angular-srcs@12.0.0-next.7 preinstall /usr/local/account/js/angular > node tools/yarn/check-yarn.js /usr/local/account/js/angular/tools/yarn/check-yarn.js:12 throw new Error( ^ Error: Please use Yarn instead of NPM to install dependencies. See: https://yarnpkg.com/lang/en/docs/install/ at Object.<anonymous> (/usr/local/account/js/angular/tools/yarn/check-yarn.js:12:9) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Function.Module.runMain (internal/modules/cjs/loader.js:831:12) at startup (internal/bootstrap/node.js:283:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! angular-srcs@12.0.0-next.7 preinstall: `node tools/yarn/check-yarn.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the angular-srcs@12.0.0-next.7 preinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /usr/local/account/.npm/_logs/2021-04-06T22_54_02_292Z-debug.log ``` to ``` $ npm install npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for angular-srcs@12.0.0-next.7: wanted: {"node":">=10.19.0 <13.0.0","yarn":">=1.22.4 <2","npm":"Plesae use yarn instead of NPM to install dependencies"} (current: {"node":"10.20.1","npm":"6.14.4"}) npm ERR! notsup Not compatible with your version of node/npm: angular-srcs@12.0.0-next.7 npm ERR! notsup Not compatible with your version of node/npm: angular-srcs@12.0.0-next.7 npm ERR! notsup Required: {"node":">=10.19.0 <13.0.0","yarn":">=1.22.4 <2","npm":"Plesae use yarn instead of NPM to install dependencies"} npm ERR! notsup Actual: {"npm":"6.14.4","node":"10.20.1"} npm ERR! A complete log of this run can be found in: npm ERR! /usr/local/account/.npm/_logs/2021-04-06T22_53_23_912Z-debug.log ``` PR Close #41477
2021-04-06 22:51:45 +00:00
"yarn": ">=1.21.1 <2",
"npm": "Please use yarn instead of NPM to install dependencies"
build: upgrade yarn to 1.3.2 (#21406) Fixes #20566 PR Close #21406
2018-01-09 10:02:03 +00:00
},
feat(aio): copy example code from angular.io
2017-02-22 18:13:21 +00:00
"keywords": [],
"author": "",
"license": "MIT",
build(docs-infra): update project structure to cli@9 12/12 (dependencies) (#36015) Update dependencies. Also, disable AOT tests for `systemjs`-type examples in Ivy mode, because our current setup does not work with v9. See #35989 for details. Fixes #34382 Fixes #34383 PR Close #36015
2020-03-17 20:28:50 +00:00
"repository": {},
feat(aio): copy example code from angular.io
2017-02-22 18:13:21 +00:00
"dependencies": {
build: update dependency typescript to ~4.8.0 (#47293) See associated pull request for more information. PR Close #47293
2022-09-06 19:23:33 +00:00
"@angular/animations": "^14.2.0",
"@angular/common": "^14.2.0",
"@angular/compiler": "^14.2.0",
"@angular/core": "^14.2.0",
"@angular/elements": "^14.2.0",
"@angular/forms": "^14.2.0",
"@angular/localize": "^14.2.0",
"@angular/platform-browser": "^14.2.0",
"@angular/platform-browser-dynamic": "^14.2.0",
"@angular/platform-server": "^14.2.0",
"@angular/router": "^14.2.0",
"@angular/service-worker": "^14.2.0",
"@angular/upgrade": "^14.2.0",
build(docs-infra): update all angular packages to use `^` instead of `~` (#47092) This forces the usage of the latest packages. PR Close #47092
2022-08-22 06:32:38 +00:00
"@nguniversal/express-engine": "^14.1.0",
refactor(docs-infra): update boilerplate to have proper `angular.js` types (#46819) With the recent lock file maintenance, the `@types/angular` dependency ended up being duplicated. This seems to happen because we locked our type dependency, but other Angular deps like `angular-route` had a looser dependency, resulting in e.g. `1.7` types and `1.8` types to be loaded. This ultimately ended up breaking TypeScript's auto-discovering of types and broke some example compilations e.g. ``` app/app.animations.ts(3,3): error TS2339: Property 'animation' does not exist on type 'IModule'. app/app.config.ts(5,45): error TS2694: Namespace 'angular' has no exported member 'route'. app/phone-detail/phone-detail.component.ajs.ts(10,37): error TS2694: Namespace 'angular' has no exported member 'route'. ``` We fix this by loosening the type dependency ranges, updating all of these. Also we update AngularJS itself to the final version. PR Close #46819
2022-07-13 14:28:55 +00:00
"angular": "^1.8.3",
build(docs-infra): update versions of some docs examples dependencies (#46609) Update angular-in-memory-web-api and jasmine-marbles (used in doc examples) to latest versions. PR Close #46609
2022-06-29 16:09:40 +00:00
"angular-in-memory-web-api": "~0.14.0",
build: update all non-major dependencies (#46707) See associated pull request for more information. PR Close #46707
2022-08-05 17:09:37 +00:00
"angular-route": "1.8.3",
docs(aio): Upgrade examples to Angular 6 (#23234) PR Close #23234
2018-04-13 02:20:01 +00:00
"core-js": "^2.5.4",
build(docs-infra): update Angular CLI/framework to v14.0.0-rc.0 in docs examples (#45997) Update the docs examples to the latest prerelease versions of Angular CLI and framework (v14.0.0-rc.0). Also update the example apps to more closely align with new CLI apps. See also the [diff][1] between a basic v13.0.0-rc.3 CLI app and a v14.0.0-rc.0 one. [1]: https://github.com/cexbrayat/angular-cli-diff/compare/13.0.0-rc.3...14.0.0-rc.0 PR Close #45997
2022-05-23 16:04:21 +00:00
"express": "^4.18.1",
"rxjs": "~7.5.0",
build(docs-infra): include `systemjs` as a dependency to SystemJS-based docs examples (#43868) Due to an oversight, the `systemjs` package was previously not included as a dependency in the boilerplate `package.json` file for SystemJS-based docs examples, despite it being required by the app. PR Close #43868
2021-11-05 17:49:51 +00:00
"systemjs": "~0.19.39",
build(docs-infra): fix SystemJS-based docs examples (#43868) Previously, the SystemJS-based docs examples (typically `ngUpgrade` examples) were not compatible with Angular v13 (due to the removal of UMD bundles from the published packages). This commit makes the examples compatible with Angular v13 and re-enables the tests for all SystemJS-based examples on CI. PR Close #43868
2021-11-05 17:49:51 +00:00
"systemjs-plugin-babel": "~0.0.25",
feat(core): drop support for TypeScript 4.2 and 4.3 (#43642) Bumps the minimum required TypeScript version to 4.4.2 and removes the integration tests for 4.1, 4.2 and 4.3. BREAKING CHANGE: TypeScript versions older than 4.4.2 are no longer supported. PR Close #43642
2021-10-02 12:51:04 +00:00
"tslib": "^2.3.0",
docs: update docs to use new zone.js entry-points (#40823) In CLI version 12, the old style of imports is no longer supported. PR Close #40823
2021-02-15 09:08:30 +00:00
"zone.js": "~0.11.4"
feat(aio): copy example code from angular.io
2017-02-22 18:13:21 +00:00
},
"devDependencies": {
build: update dependency typescript to ~4.8.0 (#47293) See associated pull request for more information. PR Close #47293
2022-09-06 19:23:33 +00:00
"@angular-devkit/build-angular": "^14.2.1",
"@angular/cli": "^14.2.1",
"@angular/compiler-cli": "^14.2.0",
build(docs-infra): update all angular packages to use `^` instead of `~` (#47092) This forces the usage of the latest packages. PR Close #47092
2022-08-22 06:32:38 +00:00
"@nguniversal/builders": "^14.1.0",
build: update dependency @rollup/plugin-commonjs to v23 (#47711) See associated pull request for more information. PR Close #47711
2022-10-10 16:44:25 +00:00
"@rollup/plugin-commonjs": "^23.0.0",
build: update systemjs aio boilerplate to work with APF v13+ `exports` field (#45405) The SystemJS examples were using an outdated version of rollup that did not support export fields. Now with the recent changes where we removed secondary package.json files, the rather old/somewhat outdated SystemJS examples failed bundling since exports were not considered. PR Close #45405
2022-04-13 08:16:37 +00:00
"@rollup/plugin-node-resolve": "^13.2.0",
refactor(docs-infra): update boilerplate to have proper `angular.js` types (#46819) With the recent lock file maintenance, the `@types/angular` dependency ended up being duplicated. This seems to happen because we locked our type dependency, but other Angular deps like `angular-route` had a looser dependency, resulting in e.g. `1.7` types and `1.8` types to be loaded. This ultimately ended up breaking TypeScript's auto-discovering of types and broke some example compilations e.g. ``` app/app.animations.ts(3,3): error TS2339: Property 'animation' does not exist on type 'IModule'. app/app.config.ts(5,45): error TS2694: Namespace 'angular' has no exported member 'route'. app/phone-detail/phone-detail.component.ajs.ts(10,37): error TS2694: Namespace 'angular' has no exported member 'route'. ``` We fix this by loosening the type dependency ranges, updating all of these. Also we update AngularJS itself to the final version. PR Close #46819
2022-07-13 14:28:55 +00:00
"@types/angular": "^1.8.4",
"@types/angular-animate": "^1.5.11",
"@types/angular-mocks": "^1.7.1",
"@types/angular-resource": "^1.5.17",
"@types/angular-route": "^1.7.2",
build(docs-infra): update Angular CLI/framework to v14.0.0-rc.0 in docs examples (#45997) Update the docs examples to the latest prerelease versions of Angular CLI and framework (v14.0.0-rc.0). Also update the example apps to more closely align with new CLI apps. See also the [diff][1] between a basic v13.0.0-rc.3 CLI app and a v14.0.0-rc.0 one. [1]: https://github.com/cexbrayat/angular-cli-diff/compare/13.0.0-rc.3...14.0.0-rc.0 PR Close #45997
2022-05-23 16:04:21 +00:00
"@types/express": "^4.17.13",
build: update all non-major dependencies (#47225) See associated pull request for more information. PR Close #47225
2022-09-01 12:44:30 +00:00
"@types/jasmine": "~4.3.0",
build: update all non-major dependencies (#46707) See associated pull request for more information. PR Close #46707
2022-08-05 17:09:37 +00:00
"@types/jquery": "3.5.14",
build(docs-infra): update Angular CLI/framework to v14.0.0-rc.0 in docs examples (#45997) Update the docs examples to the latest prerelease versions of Angular CLI and framework (v14.0.0-rc.0). Also update the example apps to more closely align with new CLI apps. See also the [diff][1] between a basic v13.0.0-rc.3 CLI app and a v14.0.0-rc.0 one. [1]: https://github.com/cexbrayat/angular-cli-diff/compare/13.0.0-rc.3...14.0.0-rc.0 PR Close #45997
2022-05-23 16:04:21 +00:00
"@types/node": "^16.11.35",
build: update `canonical-path` dependency (#26719) This new version (1.0.0) provides a typings file! PR Close #26719
2018-10-24 12:24:14 +00:00
"canonical-path": "1.0.0",
build: update dependency concurrently to v7 (#46698) | datasource | package | from | to | | ---------- | ------------ | ----- | ----- | | npm | concurrently | 5.0.1 | 7.2.2 | | npm | concurrently | 5.3.0 | 7.2.2 | PR Close #46698
2022-07-04 13:15:54 +00:00
"concurrently": "^7.0.0",
fix(docs-infra): update Angular packages to latest minor version (#45502) This is needed because Angular CLI 13.3 contains fixes that are needed for Stackblitz Node 16 to compile Sass. We also added `copyfiles` in `aio/tools/examples/shared/package.json` as `yarn sync-deps` was failing due to the missing dependency. PR Close #45502
2022-04-01 12:02:26 +00:00
"copyfiles": "^2.4.1",
build: update dependency http-server to v14 (#46572) PR Close #46572
2022-06-29 00:55:35 +00:00
"http-server": "^14.0.0",
build: update all non-major dependencies (#47487) See associated pull request for more information. PR Close #47487
2022-09-20 05:04:01 +00:00
"jasmine-core": "~4.4.0",
build(docs-infra): update versions of some docs examples dependencies (#46609) Update angular-in-memory-web-api and jasmine-marbles (used in doc examples) to latest versions. PR Close #46609
2022-06-29 16:09:40 +00:00
"jasmine-marbles": "~0.9.2",
build(docs-infra): update docs examples to Angular v12.1.3 (#42949) This commit updates the docs examples to Angular v12.1.3. In addition to updating the dependencies versions, it also updates the projects' structure and configs to more closely match what a new v12 CLI app would look like. See, also, the [diff][1] between a basic v11.2.11 CLI app and a v12.1.3 one. [1]: https://github.com/cexbrayat/angular-cli-diff/compare/11.2.11..12.1.3 PR Close #42949
2021-07-24 09:03:46 +00:00
"jasmine-spec-reporter": "~7.0.0",
build: update all non-major dependencies (#46707) See associated pull request for more information. PR Close #46707
2022-08-05 17:09:37 +00:00
"karma": "~6.4.0",
build(docs-infra): update project structure to cli@9 12/12 (dependencies) (#36015) Update dependencies. Also, disable AOT tests for `systemjs`-type examples in Ivy mode, because our current setup does not work with v9. See #35989 for details. Fixes #34382 Fixes #34383 PR Close #36015
2020-03-17 20:28:50 +00:00
"karma-chrome-launcher": "~3.1.0",
build(docs-infra): update Angular CLI/framework to v14.0.0-rc.0 in docs examples (#45997) Update the docs examples to the latest prerelease versions of Angular CLI and framework (v14.0.0-rc.0). Also update the example apps to more closely align with new CLI apps. See also the [diff][1] between a basic v13.0.0-rc.3 CLI app and a v14.0.0-rc.0 one. [1]: https://github.com/cexbrayat/angular-cli-diff/compare/13.0.0-rc.3...14.0.0-rc.0 PR Close #45997
2022-05-23 16:04:21 +00:00
"karma-coverage": "~2.2.0",
build: update all non-major dependencies (#46707) See associated pull request for more information. PR Close #46707
2022-08-05 17:09:37 +00:00
"karma-jasmine": "~5.1.0",
build: update dependency karma-jasmine-html-reporter to v2 (#46578) PR Close #46578
2022-06-29 08:21:29 +00:00
"karma-jasmine-html-reporter": "~2.0.0",
build(docs-infra): update lite-server to fix errors on OSX (#41638) ``` $ lite-server -c bs-config.aot.json $ ngc -p tsconfig-aot.json && rollup -c rollup-config.js /Users/xxxx/git/angular/aio/tools/examples/shared/node_modules/browser-sync/node_modules/chokidar/lib/fsevents-handler.js:26 return (new fsevents(path)).on('fsevent', callback).start(); ^ TypeError: fsevents is not a constructor at createFSEventsInstance (/Users/xxxx/git/angular/aio/tools/examples/shared/node_modules/browser-sync/node_modules/chokidar/lib/fsevents-handler.js:26:11) at setFSEventsListener (/Users/xxxx/git/angular/aio/tools/examples/shared/node_modules/browser-sync/node_modules/chokidar/lib/fsevents-handler.js:80:16) at FSWatcher.FsEventsHandler._watchWithFsEvents (/Users/xxxx/git/angular/aio/tools/examples/shared/node_modules/browser-sync/node_modules/chokidar/lib/fsevents-handler.js:244:16) at FSWatcher.<anonymous> (/Users/xxxx/git/angular/aio/tools/examples/shared/node_modules/browser-sync/node_modules/chokidar/lib/fsevents-handler.js:378:25) at LOOP (fs.js:1752:14) at processTicksAndRejections (internal/process/task_queues.js:79:11) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. completed: yarn serve:aot ``` PR Close #41638
2021-04-16 12:45:05 +00:00
"lite-server": "^2.6.1",
feat(aio): copy example code from angular.io
2017-02-22 18:13:21 +00:00
"lodash": "^4.16.2",
build(docs-infra): update docs examples to Angular v10 (#38993) This commit updates the docs examples to Angular v10.1.3. In addition to updating the dependencies versions, it also updates the project's structure and config to more closely match what a new v10 CLI app would look like. See, also, the [diff][1] between a basic v9.1.4 CLI app and a v10.1.3 one. [1]: https://github.com/cexbrayat/angular-cli-diff/compare/9.1.4..10.1.3 PR Close #38993
2020-09-21 17:52:26 +00:00
"protractor": "~7.0.0",
build: use the latest version of Chrome (v93) in non-bazel tests (#43880) This commit updates the version of Chrome used in non-bazel tests (via Puppeteer) to the latest (v93). PR Close #43880
2021-10-19 13:19:02 +00:00
"puppeteer": "10.2.0",
build: update dependency rimraf to v3 (#46625) | datasource | package | from | to | | ---------- | ------- | ----- | ----- | | npm | rimraf | 2.6.2 | 3.0.2 | PR Close #46625
2022-06-29 18:09:03 +00:00
"rimraf": "^3.0.0",
build: update systemjs aio boilerplate to work with APF v13+ `exports` field (#45405) The SystemJS examples were using an outdated version of rollup that did not support export fields. Now with the recent changes where we removed secondary package.json files, the rather old/somewhat outdated SystemJS examples failed bundling since exports were not considered. PR Close #45405
2022-04-13 08:16:37 +00:00
"rollup": "^2.70.1",
"rollup-plugin-terser": "^7.0.2",
build: update dependency source-map-explorer to v2 (#46626) | datasource | package | from | to | | ---------- | ------------------- | ----- | ----- | | npm | source-map-explorer | 1.5.0 | 2.5.2 | PR Close #46626
2022-06-29 19:35:38 +00:00
"source-map-explorer": "^2.0.0",
build: update all non-major dependencies (#46707) See associated pull request for more information. PR Close #46707
2022-08-05 17:09:37 +00:00
"ts-node": "~10.9.0",
build: update dependency typescript to ~4.8.0 (#47293) See associated pull request for more information. PR Close #47293
2022-09-06 19:23:33 +00:00
"typescript": "~4.8.0"
build(docs-infra): update project structure to cli@9 12/12 (dependencies) (#36015) Update dependencies. Also, disable AOT tests for `systemjs`-type examples in Ivy mode, because our current setup does not work with v9. See #35989 for details. Fixes #34382 Fixes #34383 PR Close #36015
2020-03-17 20:28:50 +00:00
}
build: allow Node.js v15 and above for local development (#42387) This commit changes the `engines` rules in the root `package.json` as well as the `package.json` used when working on docs example to also accept Node.js versions greater than v14. This aligns them with `aio/package.json` and allows using Node.js v15 and v16 (current) for local development in the `angular/angular` repo. Related to #42367. PR Close #42387
2021-05-27 13:48:45 +00:00
}
Reference in a new issue Copy permalink