search

vimalavinisha / angular2-google-chart

Angular 2 google chart
MIT License
59 stars 45 forks source link

unable to install angular2-google-chart #57

Open pkarunakar2006 opened 6 years ago

pkarunakar2006 commented 6 years ago

I am getting below error after running the command npm install angular2-google-chart, Can some one please advice how to rectify it. -- angular2-google-chart@2.3.0 +-- **UNMET PEER DEPENDENCY @angular/compiler@4.1.3 +-- UNMET PEER DEPENDENCY @angular/core@4.1.3 +-- UNMET PEER DEPENDENCY @angular/platform-browser@4.1.3 -- UNMET PEER DEPENDENCY @angular/platform-browser-dynamic@4.1.3**

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) npm WARN enoent ENOENT: no such file or directory, open 'D:\Users\pendyala.reddy\package.json' npm WARN @angular/upgrade@4.1.3 requires a peer of @angular/core@4.1.3 but none was installed. npm WARN @angular/upgrade@4.1.3 requires a peer of @angular/compiler@4.1.3 but none was installed. npm WARN @angular/upgrade@4.1.3 requires a peer of @angular/platform-browser@4.1.3 but none was installed. npm WARN @angular/upgrade@4.1.3 requires a peer of @angular/platform-browser-dynamic@4.1.3 but none was installed.

StefanoBettega commented 6 years ago

Same problem here. Even modified package.json as reported in #43 but still same error. I don't know why this ever happened; two days ago it was correctly working, and my app is referencing angular version >= 4.2.6

Update After modifying package.json and issuing some npm install, it seems that all is working now.

D3luX commented 6 years ago

Could you please share the solution? As whatever i try, i get the same error. And when running the google charts in browser, it just appears as a white screen.

StefanoBettega commented 6 years ago

I simply modified "node_modules/angular2-google-chart/package.json" changing all of the "4.1.3" strings with "^4.1.3", then I gave a npm update into the main project directory. This was sufficient to overcome the problem and get all to run again.