npm install of latest 5.0.0-rc0 fails against latest angular
See original GitHub issueBug, 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
Issue Analytics
- State:
- Created 6 years ago
- Reactions:7
- Comments:18 (6 by maintainers)
Top GitHub Comments
Finally I got everything working with this 5.0.0-rc0. 😃
Step 0: You should have Angular 5 installed which works well with Material2 Beta 12.
Step 1: install cdk@5.0.0-rc0
npm i @angular/cdk@5.0.0-rc0 --save
Step2: install material 5 npm i @angular/material@5.0.0-rc0 --save
Step 3: declare HttpClient of NG5 In systemjs.config.js, add this:
'@angular/common/http': 'npm:@angular/common/bundles/common-http.umd.js',
This is for material 5 which apparently is using HttpClient, while your app code may still be using the Http service, so you may want to keep the declaration for the Http service.
Step 4: declare the following to address a bug in rxjs 5.5.0 - 5.5.2 which NG5 and Material 5 depend on.
When testing, make sure you have proper versioning of your code and meta, or you may clear the browser caches.
Remarks: If you are using angular flex-layout, as of today, there seems to be a random bug during npm install or update, 2.0.0-rc.1 got installed instead. So goto something like YourNG2App\node_modules@angular\flex-layout and check package.json to see if it is actually “@angular/flex-layout@2.0.0-rc.1”, if it is, do the following:
npm i @angular/flex-layout
ornpm i @angular/flex-layout@2.0.0-beta.10
(cont.) If you are using Angular 5, Material2 5.0.0-rc0 and Angular Flex-layout, the following may work for you:
In package.json
In systemjs.config.js
Then run
npm install
And if you are using Angular flex-layout, please check the remarks above.