Bug, feature request, or proposal:

Since the very recent release of rc0 of 5.0.0 npm install is failing for me

What is the expected behavior?

npm install completes as it currently still does with 2.0.0-beta.12

What is the current behavior?

npm install --save @angular/material @angular/cdk

gives the following results

+-- @angular/cdk@5.0.0-rc0
+-- UNMET PEER DEPENDENCY @angular/common@4.4.6
+-- UNMET PEER DEPENDENCY @angular/core@4.4.6
+-- @angular/material@5.0.0-rc0
+-- UNMET PEER DEPENDENCY jquery@1.9.1 - 3
`-- UNMET PEER DEPENDENCY popper.js@^1.12.3

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.2
npm WARN bootstrap@4.0.0-beta.2 requires a peer of jquery@1.9.1 - 3 but none was installed.
npm WARN bootstrap@4.0.0-beta.2 requires a peer of popper.js@^1.12.3 but none was installed.
npm WARN @angular/cdk@5.0.0-rc0 requires a peer of @angular/core@^5.0.0 but none was installed.
npm WARN @angular/cdk@5.0.0-rc0 requires a peer of @angular/common@^5.0.0 but none was installed.
npm WARN @angular/material@5.0.0-rc0 requires a peer of @angular/core@^5.0.0 but none was installed.
npm WARN @angular/material@5.0.0-rc0 requires a peer of @angular/common@^5.0.0 but none was installed.

What are the steps to reproduce?

npm install --save @angular/material @angular/cdk

What is the use-case or motivation for changing an existing behavior?

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

5.0.0-rc0

Is there anything else we should know?

I am currently working round with

npm install --save @angular/material/2.0.0-beta.12 @angular/cdk/2.0.0-beta.12