`jspm install` fails with jspm v0.16.x

[chazkii]

Error when running jspm install with jspm v0.16.36, npm v3.9.3, node v6.21. Tried with jspm 0.16.34 and others downwards...

warn Running jspm globally, it is advisable to locally install jspm via npm install jspm --save-dev.
     Looking up npm:angular-powerbi
     Looking up github:angular/bower-angular

warn Using local override for github:angular/bower-angular@1.5.7
     Looking up github:twbs/bootstrap

warn Using local override for github:twbs/bootstrap@3.3.6
     Updating registry cache...
     Looking up github:angular-ui/ui-router

warn Using local override for github:angular-ui/ui-router@0.2.18
     Looking up github:frankwallis/plugin-typescript
     Downloading npm:angular-powerbi@1.0.0-beta.3

warn Error on processPackageConfig
     Package.json dependency os set to github:jspm/nodelibs-os@^0.2.0-alpha, which is not a valid dependency format for npm.
     It's advisable to publish jspm-style packages to GitHub or another registry so conventions are clear.

warn Error processing package config for npm:angular-powerbi.
     Looking up npm:typescript

warn Using local override for npm:typescript@1.8.10

err  Error processing package config for npm:angular-powerbi.

[acomsmpbot]

No issues were found in this pull request.

[mattmazzola]

Yes, this was intended to be used with 0.17.x. From what I remember there was breaking changes between 0.16 and 0.17 in the way jspm maps packages and names their config file.

I originally was trying to provide first class support for jspm by adding the jspm section to powerb-angular's package.json file which you can see here: https://github.com/Microsoft/PowerBI-Angular/blob/master/package.json but since this is not stable, it might be better to remove it and explicitly let jspm fallback to npm conventions.

For now, I think it's good to just update the README like this suggests.