skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
3283e522e439dbaeb0d2b7b97fa857589134bded
angular__angular/package.json
T

138 lines
4.2 KiB
JSON
Raw Normal View History

chore(): init project with angular-cli
2016-01-06 10:48:32 -08:00
{
chore: run travis with Node LTS version (#2786) * Switches Travis CI to the NodeJS LTS release. `6.9.4`. * Changes the package.json name for the sources to be similar as in `angular/angular`.
2017-01-24 23:16:37 +01:00
"name": "material2-srcs",
style(branding): branding consistency fixup (#2805) fixes #2803
2017-01-27 01:35:39 +02:00
"description": "Material Design components for Angular",
chore(): add `npm install` to travis.yml
2016-01-08 16:19:38 -08:00
"homepage": "https://github.com/angular/material2",
"bugs": "https://github.com/angular/material2/issues",
"repository": {
"type": "git",
"url": "https://github.com/angular/material2.git"
},
build: fix invalid required angular version (#12089)
2018-08-09 22:06:11 +02:00
"license": "MIT",
"engines": {
"node": ">= 5.4.1"
},
Add a npm script to make `npm run demo-app` do what you would expect.
2016-01-12 16:07:06 -08:00
"scripts": {
build(cdk): add bazel ng_module rules (#8370) Part of #8369
2017-11-15 11:47:56 -08:00
"postinstall": "ngc -p angular.tsconfig.json",
chore: build cdk and material in npm build task (#5376) Apparently developers that clone the Material repository to get their own version of Material are running the `npm run build` command and are expecting the CDK and Material release output to be inside of the `dist/` folder. Currently only the Material package will be built and the CDK isn't built at all. This commit changes the npm build task so that it builds every release package of the publish task. Closes #5372
2017-06-28 01:09:32 +02:00
"build": "gulp :publish:build-releases",
build: move from angular-cli to gulp (#948) Fixed #1636.
2016-08-19 10:59:45 -07:00
"demo-app": "gulp serve:devapp",
"test": "gulp test",
"tslint": "gulp lint",
"stylelint": "gulp lint",
"e2e": "gulp e2e",
build: fix deploy script in package.json (#4548)
2017-05-15 20:19:48 +02:00
"deploy": "gulp deploy:devapp",
docs: use typedoc to generate a json file documentation dump of all components (#1887)
2016-11-17 16:56:53 -05:00
"webdriver-manager": "webdriver-manager",
"docs": "gulp docs",
build: rework breaking changes tooling (#12950) * Reworks the breaking change tslint rule to remove the logic that checks that there are no expired breaking changes. * Adds a new script that can be used to get an overview of the pending and expired breaking changes.
2018-09-04 20:46:26 +02:00
"api": "gulp api-docs",
"breaking-changes": "gulp breaking-changes"
Add a npm script to make `npm run demo-app` do what you would expect.
2016-01-12 16:07:06 -08:00
},
chore: bump to 7.0.0-beta.0 w/ TS 3.0 and changelog (#12916)
2018-08-30 15:38:58 -07:00
"version": "7.0.0-beta.0",
"requiredAngularVersion": ">=7.0.0-beta.4",
chore(): init project with angular-cli
2016-01-06 10:48:32 -08:00
"dependencies": {
chore: bump to 7.0.0-beta.0 w/ TS 3.0 and changelog (#12916)
2018-08-30 15:38:58 -07:00
"@angular/animations": "7.0.0-beta.4",
"@angular/common": "7.0.0-beta.4",
"@angular/compiler": "7.0.0-beta.4",
"@angular/core": "7.0.0-beta.4",
"@angular/elements": "7.0.0-beta.4",
"@angular/forms": "7.0.0-beta.4",
"@angular/platform-browser": "7.0.0-beta.4",
chore(demo): add examples to demo app (#11018) * chore(demo): add examples to demo app * fix aot
2018-04-27 18:43:36 -07:00
"@webcomponents/custom-elements": "^1.1.0",
chore(release): update versions for RC.6 (#1149)
2016-09-01 10:14:38 -07:00
"core-js": "^2.4.1",
chore: update to RxJS 6.2.x (#12678)
2018-08-21 11:45:13 -07:00
"rxjs": "^6.2.0",
chore: bump dev dependencies (#2890) * Updates some outdated dependencies in the material2-srcs package.
2017-02-06 23:58:22 +01:00
"systemjs": "0.19.43",
build: update to TS 2.9 and enable strictFunctionTypes (#12182) Bumps the project to TypeScript 2.9, enables the `strictFunctionTypes` everywhere and fixes the various errors. Fixes #12177.
2018-08-28 16:17:26 +02:00
"tsickle": "^0.32.0",
chore: update to rxjs v6 beta and angular v6 beta (#10496)
2018-03-23 10:40:20 -05:00
"tslib": "^1.9.0",
build: fix and re-enable bazel unit tests for the cdk (#11278)
2018-05-10 17:01:04 -07:00
"zone.js": "^0.8.26"
chore(): init project with angular-cli
2016-01-06 10:48:32 -08:00
},
"devDependencies": {
feat(schematics): compatibility with Angular CLI 6.2.0 (#13078) * Upgrades the devkit dependencies to the latest versions. * Adds support for the newly introduced and published `project.targets` instead of `project.architect` (see: https://github.com/angular/angular-cli/commit/307160806cb48c95ecb8982854f452303801ac9f) * Compatibility behavior for a published but non-announced breaking change within the schematic context (see: https://github.com/angular/angular-cli/commit/9720077a4b5ae628ddfaf5f1a26bac3b04bdf637#diff-e73df838d6700d187eff76a50c7e1c53R233`) * Supports the new `project.targets` schema within the update schematics (in order to properly determine `tsconfig` files) * Due to the fact that the @angular-devkit/schematics now handles Bazel better, the template files will be resolved through NodeJS. This means that the template files need to be referenced in the @//:node_modules label. Fixes #11438
2018-09-12 00:13:35 +02:00
"@angular-devkit/core": "^0.9.0-beta.2",
"@angular-devkit/schematics": "^0.9.0-beta.2",
chore: bump to 7.0.0-beta.0 w/ TS 3.0 and changelog (#12916)
2018-08-30 15:38:58 -07:00
"@angular/bazel": "7.0.0-beta.4",
"@angular/compiler-cli": "7.0.0-beta.4",
"@angular/http": "7.0.0-beta.4",
"@angular/platform-browser-dynamic": "7.0.0-beta.4",
"@angular/platform-server": "7.0.0-beta.4",
"@angular/router": "7.0.0-beta.4",
"@angular/upgrade": "7.0.0-beta.4",
chore: add bazel test rules for the cdk (#9726) This adds bazel test rules for everything under cdk/ and sets CircleCI Overlay tests don't work because there's not yet a way to pass through flags to the browser. These issues will be addressed in a follow-up PR.
2018-02-12 16:01:00 -08:00
"@bazel/ibazel": "0.3.1",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"@google-cloud/storage": "^1.1.1",
build: remove deprecated node-github api (#12420) Switches to the newer version of `node-github` that has been renamed to `@octokit/rest`.
2018-07-31 20:13:34 +02:00
"@octokit/rest": "^15.9.4",
feat(schematics): compatibility with Angular CLI 6.2.0 (#13078) * Upgrades the devkit dependencies to the latest versions. * Adds support for the newly introduced and published `project.targets` instead of `project.architect` (see: https://github.com/angular/angular-cli/commit/307160806cb48c95ecb8982854f452303801ac9f) * Compatibility behavior for a published but non-announced breaking change within the schematic context (see: https://github.com/angular/angular-cli/commit/9720077a4b5ae628ddfaf5f1a26bac3b04bdf637#diff-e73df838d6700d187eff76a50c7e1c53R233`) * Supports the new `project.targets` schema within the update schematics (in order to properly determine `tsconfig` files) * Due to the fact that the @angular-devkit/schematics now handles Bazel better, the template files will be resolved through NodeJS. This means that the template files need to be referenced in the @//:node_modules label. Fixes #11438
2018-09-12 00:13:35 +02:00
"@schematics/angular": "^0.9.0-beta.2",
Revert "build: publish build tools on github (#5458)" (#5526) This reverts commit 0675568d03aefb1afc8cbf3df9184172e5e1bda2.
2017-07-05 18:10:22 -07:00
"@types/chalk": "^0.4.31",
chore: fix gulp-utils color issue (#8030) With (DefinitelyTyped #21004) the typings for @gulp-utils are declaring `chalk` as dependency of the types. This causes a conflict with the types from chalk and gulp fails everywhere in the CI. (https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21004) A possible solution would be locking the version of the gulp-util types to the working version `3.0.31`. As `gulp-utils` is only used in one place right now, we are just remove the `gulp-utils` import and just use `console.log` as everywhere else.
2017-10-27 19:19:25 +02:00
"@types/fs-extra": "^4.0.3",
"@types/glob": "^5.0.33",
Revert "build: publish build tools on github (#5458)" (#5526) This reverts commit 0675568d03aefb1afc8cbf3df9184172e5e1bda2.
2017-07-05 18:10:22 -07:00
"@types/gulp": "3.8.32",
chore: fix gulp-utils color issue (#8030) With (DefinitelyTyped #21004) the typings for @gulp-utils are declaring `chalk` as dependency of the types. This causes a conflict with the types from chalk and gulp fails everywhere in the CI. (https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21004) A possible solution would be locking the version of the gulp-util types to the working version `3.0.31`. As `gulp-utils` is only used in one place right now, we are just remove the `gulp-utils` import and just use `console.log` as everywhere else.
2017-10-27 19:19:25 +02:00
"@types/hammerjs": "^2.0.35",
build: bump versions of test tooling and resolve some audit warnings (#12629)
2018-08-13 15:54:52 +02:00
"@types/jasmine": "^2.8.8",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"@types/merge2": "^0.3.30",
chore: cleanup dev-dependencies (#2654) * chore: cleanup dev-dependencies * Removes unused dev-dependencies from Angular CLI-times. * Bumps versions for packages which have a newer version available. * Pushes the yarn.lock file as disucssed. * https://github.com/angular/dgeni-packages/commit/8ad91e57860b7b0ac622e82f8e6361d1ad7587d2 * Don't upgrade firebase CLI
2017-01-18 02:28:11 +01:00
"@types/minimist": "^1.2.0",
refactor(schematics): add tests for component walker (#13106) * The `ComponentWalker` is a major part of the update schematics and we should verify that external resource files are resolved properly. All test-cases currently just use inline stylesheets or templates. * Removes the `color` helper function. * Removes the superfluous utility function for retrieving a `StringLiteral`'s text content.
2018-09-13 19:43:49 +02:00
"@types/mock-fs": "^3.6.30",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"@types/node": "^7.0.21",
refactor(schematics): use parse5 for finding inputs and outputs (#12524)
2018-08-09 16:46:14 +02:00
"@types/parse5": "^5.0.0",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"@types/run-sequence": "^0.0.29",
build: replace gulp-autoprefixer (#3563) * build: replace gulp-autoprefixer * Removes `gulp-autoprefixer` in order to avoid issues with Google's internal build system. * Switches to adding vendor prefixes via SCSS mixins. * Adds a custom Stylelint plugin that utilizies Autoprefixer to find unprefixed properties, values, @rules etc. Fixes #3536. * fix: missing import * fix: address feedback
2017-03-17 19:13:38 +01:00
"autoprefixer": "^6.7.6",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"axe-webdriverjs": "^1.1.1",
Revert "build: publish build tools on github (#5458)" (#5526) This reverts commit 0675568d03aefb1afc8cbf3df9184172e5e1bda2.
2017-07-05 18:10:22 -07:00
"chalk": "^1.1.3",
chore: add missing lifecycles interfaces to declarations (#10768)
2018-05-11 14:37:11 -03:00
"codelyzer": "^4.3.0",
build: update project dependencies (#12675) * Updates Dgeni and other development dependencies in order to fix more `npm audit` vulnerabilities.
2018-08-14 19:03:36 +02:00
"dgeni": "^0.4.10",
build: update dgeni packages (#12956) * Upgrades to the latest Dgeni packages version that includes a fix which ensures that the docs for the `Platform` show up properly. See: https://github.com/angular/dgeni-packages/commit/ab957d1234b49624fb999e321479a8b7493a114a
2018-09-04 20:50:26 +02:00
"dgeni-packages": "^0.26.9",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"firebase": "^4.0.0",
"firebase-admin": "^5.0.0",
build: update project dependencies (#12675) * Updates Dgeni and other development dependencies in order to fix more `npm audit` vulnerabilities.
2018-08-14 19:03:36 +02:00
"firebase-tools": "^4.1.0",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"fs-extra": "^3.0.1",
build: add git-semver-tags to dev dependencies (#12230)
2018-07-18 17:52:58 +02:00
"git-semver-tags": "^2.0.0",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"glob": "^7.1.2",
build: stop building rxjs for closure compiler test (#6635) For every Pull Request, a job that runs the Google Closure Compiler against the demo-app will be started. In the past Closure Compiler wasn't able to properly handle CommonJS packages from the node modules. Now the Google Closure Compiler will be reconfigured to properly handle CommonJS packages (meaning that RxJS no longer needs to be built manually)
2017-08-29 01:28:50 +02:00
"google-closure-compiler": "20170409.0.0",
build: move from angular-cli to gulp (#948) Fixed #1636.
2016-08-19 10:59:45 -07:00
"gulp": "^3.9.1",
"gulp-clean": "^0.3.2",
Revert "build: publish build tools on github (#5458)" (#5526) This reverts commit 0675568d03aefb1afc8cbf3df9184172e5e1bda2.
2017-07-05 18:10:22 -07:00
"gulp-clean-css": "^3.3.1",
build: update project dependencies (#12675) * Updates Dgeni and other development dependencies in order to fix more `npm audit` vulnerabilities.
2018-08-14 19:03:36 +02:00
"gulp-cli": "^2.0.1",
chore: use gulp-connect as webserver (#2409) * No longer rebuilds all components when changes have been recognized in the dev-app. * Allows us to only reload when gulp already recognized a change (no need for filtering and extra watchers) * No longer injects CSS as the previous live-server (injecting CSS does not work for Angular 2)
2016-12-28 04:28:29 +01:00
"gulp-connect": "^5.0.0",
build: move changelog script to gulp task (#5472) * Moves the changelog script to a gulp task that includes better instructions and error reporting.
2017-08-09 08:18:38 +02:00
"gulp-conventional-changelog": "^1.1.3",
class alias tags in html generated from markdown (#3525) * class alias tags in html generated from markdown * addressed comments * address comments
2017-03-09 14:00:55 -08:00
"gulp-dom": "^0.9.17",
chore(tools): add syntax highlighting logic for examples (#2951)
2017-02-08 18:02:37 -05:00
"gulp-flatten": "^0.3.1",
Bump to gulp-highlight-files@0.0.5 (#7085)
2017-09-14 16:57:34 -07:00
"gulp-highlight-files": "^0.0.5",
Revert "build: publish build tools on github (#5458)" (#5526) This reverts commit 0675568d03aefb1afc8cbf3df9184172e5e1bda2.
2017-07-05 18:10:22 -07:00
"gulp-htmlmin": "^3.0.0",
chore: minify html and css for releases (#2262) * chore: minify html and css for releases * For releases, the HTML and CSS assets will be minified before being inlined into the built JS * Remove comments in production html
2016-12-19 19:16:28 +01:00
"gulp-if": "^2.0.2",
chore: add gulp task to convert markdown to html (#1821)
2016-11-17 09:47:58 -08:00
"gulp-markdown": "^1.2.0",
chore(tools): add syntax highlighting logic for examples (#2951)
2017-02-08 18:02:37 -05:00
"gulp-rename": "^1.2.2",
build: speed-up stylesheet building (#12426) * Switches back from `dart-sass` to `node-sass` due to a pretty huge slow-down we noticed (can be revisited) * No longer copies all SCSS files to the temporary `package` output just in favor of the demo-app (slows down unnecessarily). This now allows us to live-reload theme changes within a second. * No longer rebuilds all package SCSS files twice for the ES5 output (rel: https://github.com/angular/material2/pull/7403)
2018-07-31 18:06:39 +02:00
"gulp-sass": "^3.1.0",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"gulp-transform": "^2.0.0",
feat: angular 5 support (#6018)
2017-11-01 19:03:57 +01:00
"gulp-util": "^3.0.8",
chore: remove hammerjs types as dependency (#2369) * Removes the hammerjs types as a dependency to the @angular/material package (we don't have a dependency on hammerjs) * Improves the name in the root `package.json` to show that this pkg file is just for the development (like in Angular) * Moves hammerjs in development to the `devDependencies` because we need it always in our dev environment (same as in Angular 2)
2016-12-23 19:13:01 +01:00
"hammerjs": "^2.0.8",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"highlight.js": "^9.11.0",
build: update packaging to match angular/angular (#3751) * build: restructure release output * build: inline metadata.json resources * build: output re-export meatadata.json file in package root
2017-03-24 14:06:45 -07:00
"http-rewrite-middleware": "^0.1.6",
build: bump versions of test tooling and resolve some audit warnings (#12629)
2018-08-13 15:54:52 +02:00
"jasmine-core": "^3.2.0",
"karma": "^3.0.0",
build: disable browserstack video (#6622)
2017-08-24 19:10:06 +02:00
"karma-browserstack-launcher": "^1.3.0",
build: create coverage reports in chrome (#7714) * No longer creates the coverage reports inside of Browserstack. The reports can be generated inside of Chrome Headless that doesn't run remotely on BrowserStack or Saucelabs.
2017-10-12 23:39:52 +02:00
"karma-chrome-launcher": "^2.2.0",
build: upload coverage to firebase (#3435) * Introduces a gulp task that will run on Travis Push builds and will upload coverage results to a Firebase database. Closes #128.
2017-03-09 03:09:57 +01:00
"karma-coverage": "^1.1.1",
build: upgrade dev dependencies (#3440) * Upgrades outdated devDependencies to the latest version.
2017-03-07 01:52:56 +01:00
"karma-firefox-launcher": "^1.0.1",
build: bump versions of test tooling and resolve some audit warnings (#12629)
2018-08-13 15:54:52 +02:00
"karma-jasmine": "^1.1.2",
build: disable browserstack video (#6622)
2017-08-24 19:10:06 +02:00
"karma-sauce-launcher": "^1.2.0",
chore(karma): add support for sourcemaps (#2448)
2017-01-03 22:26:21 +01:00
"karma-sourcemap-loader": "^0.3.7",
chore: fix gulp-utils color issue (#8030) With (DefinitelyTyped #21004) the typings for @gulp-utils are declaring `chalk` as dependency of the types. This causes a conflict with the types from chalk and gulp fails everywhere in the CI. (https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21004) A possible solution would be locking the version of the gulp-util types to the working version `3.0.31`. As `gulp-utils` is only used in one place right now, we are just remove the `gulp-utils` import and just use `console.log` as everywhere else.
2017-10-27 19:19:25 +02:00
"magic-string": "^0.22.4",
chore(tslint): use globs for custom rule source file filtering (#6235) A few custom TSLint rules already accept an option array that can be used to whitelist specific files. These whitelists are based on normal Regular Expressions which do not work very well for path matching. This commit changes the existing whitelists to use minimatch, which is a package that allows matching strings/paths against globs. For rules like `requireLicenseBanner` where the whitelist is hardcoded right now, the whitelist has been introduced as well.
2017-08-04 23:00:29 +02:00
"minimatch": "^3.0.4",
chore: fix publish gulp task and output more information. (#1099)
2016-08-22 14:18:24 -07:00
"minimist": "^1.2.0",
refactor(schematics): add tests for component walker (#13106) * The `ComponentWalker` is a major part of the update schematics and we should verify that external resource files are resolved properly. All test-cases currently just use inline stylesheets or templates. * Removes the `color` helper function. * Removes the superfluous utility function for retrieving a `StringLiteral`'s text content.
2018-09-13 19:43:49 +02:00
"mock-fs": "^4.7.0",
feat(datepicker): Add Moment.js adapter (#6860) * create moment adapter * add Moment to karma.conf.js * use MAT_DATE_LOCALE * tests are now running * add in tests * WIP: demo * add synthetic default imports for moment * add locale switching to demo * fix moment import issues with tests * fix aot * address comments * fix closure issue * add additional explanation of rollup issue * remove moment adapter demo since it is preventing sync into g3 (will add back as a docs example in future PR). * fix bad rebase
2017-09-12 13:24:23 -07:00
"moment": "^2.18.1",
build: bump versions of test tooling and resolve some audit warnings (#12629)
2018-08-13 15:54:52 +02:00
"node-sass": "^4.9.3",
fix: parse5 not listed as dependency for material (#11981)
2018-06-29 20:04:44 +02:00
"parse5": "^5.0.0",
build: bump versions of test tooling and resolve some audit warnings (#12629)
2018-08-13 15:54:52 +02:00
"protractor": "^5.4.0",
chore: fix gulp-utils color issue (#8030) With (DefinitelyTyped #21004) the typings for @gulp-utils are declaring `chalk` as dependency of the types. This causes a conflict with the types from chalk and gulp fails everywhere in the CI. (https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21004) A possible solution would be locking the version of the gulp-util types to the working version `3.0.31`. As `gulp-utils` is only used in one place right now, we are just remove the `gulp-utils` import and just use `console.log` as everywhere else.
2017-10-27 19:19:25 +02:00
"request": "^2.83.0",
build: move from angular-cli to gulp (#948) Fixed #1636.
2016-08-19 10:59:45 -07:00
"resolve-bin": "^0.4.0",
build: add package name to AMD modules (#10177) * Fixes that the UMD bundles, which use the `define` function in AMD mode, don't have a module name. This feature has been added in later versions of Rollup, so we had to upgrade. By comparing with the previous UMD bundles, the bundles still seem to work properly (also in our demo-app). Fixes #10142
2018-02-28 20:15:16 +01:00
"rollup": "^0.56.3",
"rollup-plugin-alias": "^1.4.0",
"rollup-plugin-node-resolve": "^3.0.3",
build: move from angular-cli to gulp (#948) Fixed #1636.
2016-08-19 10:59:45 -07:00
"run-sequence": "^1.2.2",
build: dedupe theming scss bundle (#4174) Fixes #3931
2017-04-21 03:45:01 +02:00
"scss-bundle": "^2.0.1-beta.7",
chore: fix gulp-utils color issue (#8030) With (DefinitelyTyped #21004) the typings for @gulp-utils are declaring `chalk` as dependency of the types. This causes a conflict with the types from chalk and gulp fails everywhere in the CI. (https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21004) A possible solution would be locking the version of the gulp-util types to the working version `3.0.31`. As `gulp-utils` is only used in one place right now, we are just remove the `gulp-utils` import and just use `console.log` as everywhere else.
2017-10-27 19:19:25 +02:00
"selenium-webdriver": "^3.6.0",
Revert "build: publish build tools on github (#5458)" (#5526) This reverts commit 0675568d03aefb1afc8cbf3df9184172e5e1bda2.
2017-07-05 18:10:22 -07:00
"sorcery": "^0.10.0",
build: disallow namespace usage and bump stylelint (#9022)
2017-12-22 16:27:12 +01:00
"stylelint": "^8.4.0",
build: upgrade dev dependencies (#4707) * build: upgrade dev dependencies * Upgrades outdated development dependencies to the latest versions. * Skipped upgrading Autoprefixer due to a breaking change with the Browserlist. * Skipped upgrading UglifyJS due to unresolved issues in UglifyJS3 * Skipped upgrading google-closure-compiler due to https://github.com/alexeagle/closure-compiler-angular-bundling/issues/30 * Skipped upgrading jasmine types because they now enforce types in `expect` calls (which is nice) but for Protractor the `expect` automatically unwraps promises (See https://github.com/angular/protractor/issues/4176) * Lock jasmine types
2017-05-22 23:59:11 +02:00
"ts-node": "^3.0.4",
chore: fix gulp-utils color issue (#8030) With (DefinitelyTyped #21004) the typings for @gulp-utils are declaring `chalk` as dependency of the types. This causes a conflict with the types from chalk and gulp fails everywhere in the CI. (https://github.com/DefinitelyTyped/DefinitelyTyped/issues/21004) A possible solution would be locking the version of the gulp-util types to the working version `3.0.31`. As `gulp-utils` is only used in one place right now, we are just remove the `gulp-utils` import and just use `console.log` as everywhere else.
2017-10-27 19:19:25 +02:00
"tsconfig-paths": "^2.3.0",
chore: bump to latest tslint version (#12300)
2018-07-21 02:27:42 +02:00
"tslint": "^5.11.0",
chore: bump to 7.0.0-beta.0 w/ TS 3.0 and changelog (#12916)
2018-08-30 15:38:58 -07:00
"typescript": "3.0.3",
chore: remove references to the web animations polyfill (#11179) Gets rid of the Web animations polyfill from our demo apps, as well as from the docs. The polyfill is not longer required as of Angular 6.
2018-05-08 18:59:01 +02:00
"uglify-js": "^2.8.14"
chore(): init project with angular-cli
2016-01-06 10:48:32 -08:00
}
}
Reference in New Issue Copy Permalink