Unit tests process crashes

[dahaupt]

Bug, feature request, or proposal:

Bug

What is the expected behavior?

The unit tests should work on master branch.

What is the current behavior?

The process fails in step :build:components:spec with:

node_modules/@types/jasmine/index.d.ts(39,38): error TS2371: A parameter initializer is only allowed in a function or constructor implementation.
node_modules/@types/jasmine/index.d.ts(39,46): error TS2304: Cannot find name 'keyof'.
node_modules/@types/jasmine/index.d.ts(39,52): error TS1005: '=' expected.

What are the steps to reproduce?

Run gulp test on the master branch.

Which versions of Angular, Material, OS, browsers are affected?

Latest Version of Material, Windows 10, Angular 2.4.7

Is there anything else we should know?

I'm no expert in unit tests, but simply starting them on a new cloned repository should work (e2e tests are working fine). It could be possible too, that this is just a problem on my system, because otherwise someone would have already noticed this.

[modernfidelity]

I'll also getting this via -> gulp build:release at the "Starting ':build:components:ngc'" step

[kara]

Running tests works for me on master. What version of node are you running? I'm running 6.2.2.

[dahaupt]

@kara I'm running version v6.9.5 of node (latest).

[trshafer]

I have the same issue. I'm running 6.9.4, as that is what travis is running on: https://github.com/angular/material2/blob/master/.travis.yml#L5

[kara]

How about Typescript versions? I'm doing a fresh npm install now from scratch to see if that breaks anything..

[dahaupt]

My global Typescript version is 2.1.5, in the project (master) it is 2.0.10. I'm not sure which one is used for tests.

[trshafer]

Did a git bisect of "npm install && npm test". This is the commit where it changed from a warning to an error 4a4261e.

[kara]

Okay, just blew away my node modules and started from scratch. Also getting the error now.

[modernfidelity]

Solved this by reducing the @types/jasmine to 2.5.38

…

Sent from my iPhone

On 13 Feb 2017, at 17:50, Kara ***@***.***> wrote: Okay, just blew away my node modules and started from scratch. Also getting the error now. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[owlstack]

I'm having the same issue. Is this resolved? should I wait for latest release?

[trshafer]

@owlstack, are you still getting the issue with #3080 merged in? Did you remove your node_modules folder and re install?

[Slashmsu]

I have the same error, I removed node_modules and reinstalled it, but I still have this error

[jppellerin]

I had this issue and I can confirm that going back down to 2.5.38 resolved it.

[angular-automatic-lock-bot]

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.}