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

75 lines
2.6 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
"angular-cli": {},
"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": "yarn check-env && yarn docs && ng build -prod -sm",
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",
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
"lint": "yarn check-env && ng lint",
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",
ci(aio): add initial implementation for aio-builds setup
2017-02-06 13:40:28 -05:00
"deploy-preview": "scripts/deploy-preview.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
"deploy-staging": "firebase use staging --token \"$FIREBASE_TOKEN\" && yarn ~~deploy",
"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 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
"docs": "dgeni ./transforms/angular.io-package",
refactor(aio): re-arrange npm scripts
2017-03-13 06:48:04 -04:00
"docs-test": "node ../dist/tools/cjs-jasmine/index-tools ../../transforms/**/*.spec.js",
"~~update-webdriver": "webdriver-manager update --standalone false --gecko false",
revert: build(aio): implement prerendering (#15346) This reverts commit d0bc83ca275964fa1de6684c3cdc6714de386efd. Protractor-based prerendering is flakey on Travis and takes several minutes to complete, slowing down the build. Prerendering has a lower impact now that we use a ServiceWorker. We will revisit in the future (probably using a `PlatformServer`-based approach). PR Close #15346
2017-03-21 09:46:20 -04:00
"pre~~deploy": "yarn build",
refactor(aio): re-arrange npm scripts
2017-03-13 06:48:04 -04:00
"~~deploy": "firebase deploy --message \"Commit: $TRAVIS_COMMIT\" --non-interactive --token \"$FIREBASE_TOKEN\""
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 CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"@angular/material": "https://github.com/angular/material2-builds",
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: update to angular 4.0.0-rc.4 and service-worker@1.0.0-beta.7
2017-03-17 00:16:41 -04:00
"@angular/service-worker": "^1.0.0-beta.7",
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): use forked version of Rho rendering engine The original Rho is too strict when it comes to markdown headings. It requires that there be a blank line separating the heading and the next paragraph. The forked version here fixes that; but the Rho project will not merge it as it goes against there basic rules.
2017-03-19 06:39:40 -04:00
"rho": "https://github.com/petebacondarwin/rho#heading-fix",
build(aio): upgrade to rxjs@5.2.0
2017-03-21 11:31:46 -04:00
"rxjs": "^5.2.0",
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
"ts-helpers": "^1.1.1",
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 1.0.0-rc.4
2017-03-21 00:32:50 -04:00
"@angular/cli": "^1.0.0-rc.4",
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): 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): upgrade to CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"codelyzer": "~2.0.0-beta.4",
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",
ci(aio): deploy from CI to staging
2017-01-25 12:39:01 -05:00
"firebase-tools": "^3.2.1",
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
"gulp": "^3.9.1",
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",
"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",
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): 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): upgrade to CLI beta.32 and MD beta.2
2017-02-20 22:05:40 -05:00
"ts-node": "~2.0.0",
"tslint": "~4.4.2",
build(aio): upgrade to angular 4.0.0-rc.2
2017-03-02 15:39:19 -05:00
"typescript": "2.1.6"
build(aio): add angular.io package.json and yarn.lock file closes #14098
2017-01-25 06:04:30 -05:00
}
}