honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/aio/package.json

95 lines
3.5 KiB
JSON
Raw Normal View History

build(aio): add angular.io package.json and yarn.lock file closes #14098
2017-01-25 06:04:30 -05:00
{
"name": "angular.io",
"version": "0.0.0",
ci(aio): deploy from CI to staging
2017-01-25 12:39:01 -05:00
"main": "index.js",
"repository": "git@github.com:angular/angular.git",
"author": "Angular",
build(aio): add angular.io package.json and yarn.lock file closes #14098
2017-01-25 06:04:30 -05:00
"license": "MIT",
feat(aio): add initial angular-cli scaffold (#14118) - adds initial CLI-generated app - adds material toolbar - initial (very rough) scss setup, lifted from angular/material - initial routing scaffold w/ homepage
2017-01-27 03:20:51 -05:00
"scripts": {
build(aio): move gulp tasks to package.json Generate the docs with `yarn docs`. Test the doc generation code with `yarn docs-test` The docs are automatically built as part of the `yarn build` task, so there is no need to rebuild them in the test_aio.sh file
2017-03-03 06:18:15 -05:00
"ng": "yarn check-env && ng",
"start": "yarn check-env && ng serve",
build(aio): add setup script
2017-04-19 08:02:35 -04:00
"build": "yarn check-env && yarn setup && ng build -prod -sm",
test(aio): enable linting of `transforms/` and add rules for jasmine
2017-04-01 14:34:10 -04:00
"lint": "yarn check-env && yarn docs-lint && ng lint",
build(aio): `yarn test --sourcemap=false` for faster dev/test cycles
2017-03-14 15:59:58 -04:00
"test": "yarn check-env && ng test --sourcemap=false",
refactor(aio): re-arrange npm scripts
2017-03-13 06:48:04 -04:00
"pree2e": "yarn ~~update-webdriver",
build(aio): move gulp tasks to package.json Generate the docs with `yarn docs`. Test the doc generation code with `yarn docs-test` The docs are automatically built as part of the `yarn build` task, so there is no need to rebuild them in the test_aio.sh file
2017-03-03 06:18:15 -05:00
"e2e": "yarn check-env && ng e2e --no-webdriver-update",
build(aio): add setup script
2017-04-19 08:02:35 -04:00
"setup": "yarn && yarn boilerplate:add && yarn docs && yarn generate-plunkers && yarn generate-zips",
ci(aio): verify that the Lighthouse PWA score remains above a threshold
2017-03-31 19:24:25 -04:00
"pretest-pwa-score-local": "yarn build",
"test-pwa-score-local": "concurrently --kill-others --success first \"http-server dist -p 4200 --silent\" \"yarn test-pwa-score -- http://localhost:4200 90\"",
"test-pwa-score": "node scripts/test-pwa-score",
ci(aio): add initial implementation for aio-builds setup
2017-02-06 13:40:28 -05:00
"deploy-preview": "scripts/deploy-preview.sh",
ci(aio): convert `deploy-staging` to a shell script
2017-04-01 08:09:39 -04:00
"deploy-staging": "scripts/deploy-staging.sh",
build(aio): move gulp tasks to package.json Generate the docs with `yarn docs`. Test the doc generation code with `yarn docs-test` The docs are automatically built as part of the `yarn build` task, so there is no need to rebuild them in the test_aio.sh file
2017-03-03 06:18:15 -05:00
"check-env": "node ../tools/check-environment.js",
build(aio): delete content folder before doc-gen (#15414) This should prevent false-positive e2e test runs where stale files are left lying around.
2017-03-23 13:23:09 -04:00
"predocs": "rimraf src/content",
build(aio): move the `transforms` folder into the `tools` folder
2017-04-16 16:31:21 -04:00
"docs": "dgeni ./tools/transforms/angular.io-package",
"docs-watch": "node tools/transforms/authors-package/watchr.js",
"docs-lint": "eslint --ignore-path=\"tools/transforms/.eslintignore\" tools/transforms",
"docs-test": "node ../dist/tools/cjs-jasmine/index-tools ../../tools/transforms/**/*.spec.js",
refactor(aio): re-arrange npm scripts
2017-03-13 06:48:04 -04:00
"~~update-webdriver": "webdriver-manager update --standalone false --gecko false",
build(aio): update boilerplate to new folder structure
2017-04-02 10:53:41 -04:00
"boilerplate:add": "node ./tools/examples/add-example-boilerplate add",
build(aio): ability to generate plunkers
2017-03-28 13:29:47 -04:00
"boilerplate:remove": "node ./tools/examples/add-example-boilerplate remove",
build(aio): ability to generate zips
2017-04-16 17:40:47 -04:00
"generate-plunkers": "node ./tools/plunker-builder/generatePlunkers",
"generate-zips": "node ./tools/example-zipper/generateZips"
feat(aio): add initial angular-cli scaffold (#14118) - adds initial CLI-generated app - adds material toolbar - initial (very rough) scss setup, lifted from angular/material - initial routing scaffold w/ homepage
2017-01-27 03:20:51 -05:00
},
"private": true,
"dependencies": {
build(aio): upgrade to angular 4.0.0-rc.2
2017-03-02 15:39:19 -05:00
"@angular/animations": "next",
"@angular/common": "next",
"@angular/compiler": "next",
"@angular/core": "next",
"@angular/forms": "next",
"@angular/http": "next",
build(aio): upgrade to @angular/material#2.0.0-beta.3 (#15606)
2017-04-12 15:25:11 -04:00
"@angular/material": "^2.0.0-beta.3",
build(aio): upgrade to angular 4.0.0-rc.2
2017-03-02 15:39:19 -05:00
"@angular/platform-browser": "next",
"@angular/platform-browser-dynamic": "next",
"@angular/platform-server": "next",
"@angular/router": "next",
build(aio): upgrade @angular/service-worker to v1.0.0-beta.8
2017-03-24 10:20:23 -04:00
"@angular/service-worker": "^1.0.0-beta.8",
feat(aio): add initial angular-cli scaffold (#14118) - adds initial CLI-generated app - adds material toolbar - initial (very rough) scss setup, lifted from angular/material - initial routing scaffold w/ homepage
2017-01-27 03:20:51 -05:00
"core-js": "^2.4.1",
build(aio): upgrade to rxjs@5.2.0
2017-03-21 11:31:46 -04:00
"rxjs": "^5.2.0",
build(aio): update @angular to 4.0.0-rc.5 and zone.js to 0.8.4
2017-03-21 00:29:48 -04:00
"zone.js": "^0.8.4"
feat(aio): add initial angular-cli scaffold (#14118) - adds initial CLI-generated app - adds material toolbar - initial (very rough) scss setup, lifted from angular/material - initial routing scaffold w/ homepage
2017-01-27 03:20:51 -05:00
},
build(aio): add angular.io package.json and yarn.lock file closes #14098
2017-01-25 06:04:30 -05:00
"devDependencies": {
build(aio): upgrade @angular/cli to v1.0.0
2017-03-24 10:15:44 -04:00
"@angular/cli": "^1.0.0",
build(aio): upgrade to angular 4.0.0-rc.2
2017-03-02 15:39:19 -05:00
"@angular/compiler-cli": "next",
feat(aio): add initial angular-cli scaffold (#14118) - adds initial CLI-generated app - adds material toolbar - initial (very rough) scss setup, lifted from angular/material - initial routing scaffold w/ homepage
2017-01-27 03:20:51 -05:00
"@types/jasmine": "2.5.38",
build(aio): upgrade to CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"@types/node": "~6.0.60",
build(aio): ability to generate zips
2017-04-16 17:40:47 -04:00
"archiver": "^1.3.0",
build(aio): big move of docs related files (#14361) All the docs related files (docs-app, doc-gen, content, etc) are now to be found inside the `/aio` folder. The related gulp tasks have been moved from the top level gulp file to a new one inside the `/aio` folder. The structure of the `/aio` folder now looks like: ``` /aio/ build/ # gulp tasks content/ #MARKDOWN FILES for devguides, cheatsheet, etc devguides/ cheatsheets/ transforms/ #dgeni packages, templates, etc src/ app/ assets/ content/ #HTML + JSON build artifacts produced by dgeni from /aio/content. #This dir is .gitignored-ed e2e/ #protractor tests for the doc viewer app node_modules/ #dependencies for both the doc viewer builds and the dgeni stuff #This dir is .gitignored-ed gulpfile.js #Tasks for generating docs and building & deploying the doc viewer ``` Closes #14361
2017-02-09 14:58:36 -05:00
"canonical-path": "^0.0.2",
build(aio): update project config for @angular/cli v1.0.0 This is a follow-up to 487a0e1. The changes are based on [this wiki entry][1]. [1]: https://github.com/angular/angular-cli/wiki/stories-1.0-update.
2017-03-27 12:13:50 -04:00
"codelyzer": "~2.0.0",
ci(aio): verify that the Lighthouse PWA score remains above a threshold
2017-03-31 19:24:25 -04:00
"concurrently": "^3.4.0",
build(aio): update dgeni-packages to 0.16.8 (#14597)
2017-02-22 14:27:09 -05:00
"dgeni": "^0.4.7",
build(aio): update to dgeni-packages 0.17.0 This new version fixes the problem with mistaking content inside inline HTML blocks as tags Related to #15199
2017-03-17 12:48:59 -04:00
"dgeni-packages": "0.17.0",
build(aio): big move of docs related files (#14361) All the docs related files (docs-app, doc-gen, content, etc) are now to be found inside the `/aio` folder. The related gulp tasks have been moved from the top level gulp file to a new one inside the `/aio` folder. The structure of the `/aio` folder now looks like: ``` /aio/ build/ # gulp tasks content/ #MARKDOWN FILES for devguides, cheatsheet, etc devguides/ cheatsheets/ transforms/ #dgeni packages, templates, etc src/ app/ assets/ content/ #HTML + JSON build artifacts produced by dgeni from /aio/content. #This dir is .gitignored-ed e2e/ #protractor tests for the doc viewer app node_modules/ #dependencies for both the doc viewer builds and the dgeni stuff #This dir is .gitignored-ed gulpfile.js #Tasks for generating docs and building & deploying the doc viewer ``` Closes #14361
2017-02-09 14:58:36 -05:00
"entities": "^1.1.1",
test(aio): enable linting of `transforms/` and add rules for jasmine
2017-04-01 14:34:10 -04:00
"eslint": "^3.19.0",
"eslint-plugin-jasmine": "^2.2.0",
ci(aio): deploy from CI to staging
2017-01-25 12:39:01 -05:00
"firebase-tools": "^3.2.1",
build(aio): copy examples boilerplate
2017-03-15 17:41:15 -04:00
"fs-extra": "^2.1.1",
"globby": "^6.1.0",
test(aio): enable tslint rule for focused jasmine tests/suites
2017-04-01 14:32:48 -04:00
"html": "^1.0.0",
ci(aio): verify that the Lighthouse PWA score remains above a threshold
2017-03-31 19:24:25 -04:00
"http-server": "^0.9.0",
build(aio): upgrade to CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"jasmine-core": "~2.5.2",
"jasmine-spec-reporter": "~3.2.0",
build(aio): ability to generate plunkers
2017-03-28 13:29:47 -04:00
"jsdom": "^9.12.0",
build(aio): upgrade to CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"karma": "~1.4.1",
"karma-chrome-launcher": "~2.0.0",
"karma-cli": "~1.0.1",
"karma-coverage-istanbul-reporter": "^0.2.0",
"karma-jasmine": "~1.1.0",
"karma-jasmine-html-reporter": "^0.2.2",
ci(aio): verify that the Lighthouse PWA score remains above a threshold
2017-03-31 19:24:25 -04:00
"lighthouse": "^1.6.3",
build(aio): big move of docs related files (#14361) All the docs related files (docs-app, doc-gen, content, etc) are now to be found inside the `/aio` folder. The related gulp tasks have been moved from the top level gulp file to a new one inside the `/aio` folder. The structure of the `/aio` folder now looks like: ``` /aio/ build/ # gulp tasks content/ #MARKDOWN FILES for devguides, cheatsheet, etc devguides/ cheatsheets/ transforms/ #dgeni packages, templates, etc src/ app/ assets/ content/ #HTML + JSON build artifacts produced by dgeni from /aio/content. #This dir is .gitignored-ed e2e/ #protractor tests for the doc viewer app node_modules/ #dependencies for both the doc viewer builds and the dgeni stuff #This dir is .gitignored-ed gulpfile.js #Tasks for generating docs and building & deploying the doc viewer ``` Closes #14361
2017-02-09 14:58:36 -05:00
"lodash": "^4.17.4",
build(aio): upgrade to CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"protractor": "~5.1.0",
build(aio): implement the remark renderer The implementation adds three plugins to the remark processor: * remove support for code blocks triggered by indented text - only gfm triple backticks are supported; and also adds support for dgeni inline tags. * ignore content within `code-example` and `code-tabs` elements. This prevents the content being accidentally treated as markdown * ignore dgeni inline tags, e.g. `{@link ... }` to prevent the content of the links from being accidentally treated as markdown
2017-04-11 13:24:08 -04:00
"remark": "^7.0.0",
"remark-html": "^6.0.0",
build(aio): do not HTML format code-example contents (#15554) The markdown renderer passes its output through an HTML pretty printer. While this is good in most cases, it makes a mess of elements that expect their content to be left untouched. The pretty printer already ignores `pre` tags (and other built-ins) by default. This fix allows us to specify other tags that should be left alone. Further it actually specifies this option for `code-example` and `code-pane` tags, which expect to contain preformatted content.
2017-03-28 11:22:44 -04:00
"rho": "https://github.com/petebacondarwin/rho#master",
build(aio): delete content folder before doc-gen (#15414) This should prevent false-positive e2e test runs where stale files are left lying around.
2017-03-23 13:23:09 -04:00
"rimraf": "^2.6.1",
build(aio): copy examples boilerplate
2017-03-15 17:41:15 -04:00
"shelljs": "^0.7.7",
build(aio): upgrade to CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"ts-node": "~2.0.0",
build(aio): update project config for @angular/cli v1.0.0 This is a follow-up to 487a0e1. The changes are based on [this wiki entry][1]. [1]: https://github.com/angular/angular-cli/wiki/stories-1.0-update.
2017-03-27 12:13:50 -04:00
"tslint": "~4.5.0",
test(aio): enable tslint rule for focused jasmine tests/suites
2017-04-01 14:32:48 -04:00
"typescript": "2.2.0",
build(aio): add `doc-watch` yarn task for docs authors This task is suitable for day to day docs authoring. This task cuts corners, which makes it much faster than a full `yarn docs` run but it does not produce completely valid output. In general this isgood enough for authors to see their changes as they make them. The task is triggered by a call to ``` yarn docs-watch ``` This sets up watchers on the `aio/contents` and `packages` folders. Any changes to files below these folders new doc generation run to start. The input to the generation is confined to a collection of files related to the changed file. For example: * a change to a file in `aio/content/marketing` will generate all the marketing files. * a change to a file in `aio/content/tutorial` or `aio/examples/toh-*` will generate all the tutorial files (and their embedded examples). * a change to a file in `aio/guide` or `aio/examples` (but not a `toh-` example) will generate the appropriate guide and its embedded examples * a change to a file in `packages` or `packages/examples` will generate the appropriate API doc and its embedded examples. Be aware that the mapping between docs and its examples are based on doc file and example folder structure being equivalent. Sometimes a doc will reference an example in a different folder, in which case the generated doc will be inaccurate. Mostly this is not a big problem.
2017-04-16 15:48:22 -04:00
"vrsource-tslint-rules": "^4.0.1",
"watchr": "^3.0.1"
build(aio): add angular.io package.json and yarn.lock file closes #14098
2017-01-25 06:04:30 -05:00
}
}