Closed code-tree closed 7 years ago
It is not due to Angular 2.3 but is due to the latest version of some other package. I froze all the versions and only upgraded Angular and a couple of others, and got it working. Here is my config that it worked successfully with:
"dependencies": {
"@angular/common": "2.3.0",
"@angular/compiler": "2.3.0",
"@angular/core": "2.3.0",
"@angular/forms": "2.3.0",
"@angular/http": "2.3.0",
"@angular/platform-browser": "2.3.0",
"@angular/platform-browser-dynamic": "2.3.0",
"@angular/router": "3.3.0",
"core-js": "2.4.1",
"hammerjs": "2.0.8",
"rxjs": "5.0.0-beta.12",
"systemjs": "0.19.38",
"zone.js": "0.6.23"
},
"devDependencies": {
"@angular/compiler-cli": "2.3.0",
"@angular/platform-server": "2.3.0",
"@types/glob": "5.0.29",
"@types/gulp": "3.8.29",
"@types/hammerjs": "2.0.30",
"@types/jasmine": "^2.2.31",
"@types/merge2": "0.0.28",
"@types/minimist": "1.1.28",
"@types/node": "6.0.34",
"@types/run-sequence": "0.0.27",
"@types/rx": "2.5.33",
"conventional-changelog": "1.1.0",
"express": "4.14.0",
"firebase-tools": "2.2.1",
"fs-extra": "0.26.5",
"glob": "6.0.4",
"gulp": "3.9.1",
"gulp-autoprefixer": "3.1.1",
"gulp-clean": "0.3.2",
"gulp-cli": "1.2.2",
"gulp-markdown": "1.2.0",
"gulp-sass": "2.3.2",
"gulp-server-livereload": "1.8.2",
"gulp-shell": "0.5.2",
"gulp-sourcemaps": "1.6.0",
"gulp-transform": "1.1.0",
"gulp-typescript": "2.13.6",
"jasmine-core": "^2.4.1",
"karma": "1.1.1",
"karma-browserstack-launcher": "1.0.1",
"karma-chrome-launcher": "1.0.1",
"karma-firefox-launcher": "1.0.0",
"karma-jasmine": "1.0.2",
"karma-sauce-launcher": "1.0.0",
"madge": "0.6.0",
"merge2": "1.0.2",
"minimist": "1.2.0",
"node-sass": "^3.4.2",
"protractor": "4.0.8",
"protractor-accessibility-plugin": "0.1.1",
"resolve-bin": "0.4.0",
"rollup": "0.34.13",
"run-sequence": "1.2.2",
"sass": "^0.5.0",
"strip-ansi": "3.0.0",
"stylelint": "7.5.0",
"symlink-or-copy": "1.0.1",
"travis-after-modes": "0.0.5",
"ts-node": "0.7.3",
"tslint": "3.13.0",
"typedoc": "0.5.1",
"typescript": "2.0.2",
"typings": "1.3.1",
"which": "1.2.4"
}
Had exactly same problem here. And I used exactly same solution as yours :)
Thank you.
Ok, I figured out it is due to Typescript 2.1
https://github.com/angular/angular/pull/13294
Should typescript version be pinned down until this is fixed?
Until Angular officially supports TypeScript > 2.1 I would say yes. That said, I have been running with TypeScript pinned for quite some time.
At the very least, adding a note somewhere about TypeScript compatibility would be a good idea. I've seen the TypeScript 2.1 thing pop up all over the place.
Closing this as it's an issue w/ ngc
rather than Material. Our dep on typescript
is now stuck to the appropriate version.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
Bug, feature request, or proposal:
Bug
What is the expected behavior?
gulp build:release
builds successfullyWhat is the current behavior?
It raises the following (after a fresh delete and install of all node_modules)
What are the steps to reproduce?
Which versions of Angular, Material, OS, browsers are affected?
86123a3f0ca5bc3f3cf5f1b1f2263564c861af2a
Is there anything else we should know?
Result of
npm install