Zone.js and rxjs dependencies are causing issues when working with other 3rd party libraries

I’m submitting a … (check one with “x”)

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior I’m having dependency issues caused by zone.js and rxjs. My package.json file is:

{
  "jspm": {
    "dependencies": {
      "@angular/common": "npm:@angular/common@^2.3.1",
      "@angular/compiler": "npm:@angular/compiler@^2.3.1",
      "@angular/core": "npm:@angular/core@^2.3.1",
      "@angular/platform-browser": "npm:@angular/platform-browser@^2.3.1",
      "@angular/platform-browser-dynamic": "npm:@angular/platform-browser-dynamic@^2.3.1",
      "@angular/router": "npm:@angular/router@^3.3.1",
      "angular2-google-maps": "npm:angular2-google-maps@^0.16.0",
      "core-js": "npm:core-js@^2.4.1",
      "hammerjs": "npm:hammerjs@^2.0.8",
      "ng2-simple-timer": "npm:ng2-simple-timer@^1.2.5",
      "reflect-metadata": "npm:reflect-metadata@^0.1.8",
      "rxjs": "npm:rxjs@5.0.0-rc.4",
      "zone.js": "npm:zone.js@^0.7.2"
    },
    "devDependencies": {
      "@types/core-js": "npm:@types/core-js@^0.9.35",
      "@types/node": "npm:@types/node@^6.0.52",
      "typescript": "npm:typescript@^2.1.4"
    }
  }
}

Now in the npm log I have:

npm WARN ng2-simple-timer@1.2.5 requires a peer of rxjs@5.0.0-beta.12 but none was installed.
npm WARN ng2-simple-timer@1.2.5 requires a peer of zone.js@^0.6.6 but none was installed.
npm WARN angular2-google-maps@0.16.0 requires a peer of zone.js@^0.6.25 but none was installed.

As you can see basically I should install rxjs@5.0.0-beta.12 and rxjs@5.0.0-rc.4 AND zone.js@^0.6.6, zone.js@^0.6.25 and zone.js@^0.7.2 to be able to fulfill every dependency for every library that I use. Now I have only 2 libraries. But how about if I would depend on 10 libraries? I guess you see the point.

Expected behavior Maybe it’s not directly connected to angular2, but I also don’t find any instructions on the net how to solve this issue. It’s also not a solution that I should go to those 3rd parties asking for an upgrade. I should ask then 10 3rd party? What if the maintainer has gone away? (the code would just work fine with the upgraded zone and rxjs) Once everybody has upgraded, and Angular moves forward the whole round begins from the beginning…

What I could imagine is that zone.js and rxjs shouldn’t be dependencies (don’t know that is it possible) at all for the 3rd party libraries. But in such a case the documentation should strongly highlight it.

• Angular version: 2.3.1

[PeterOsifeso]

Me too

[ashleymorris2]

+1