Kinvey backend / RC0: Typings or rollup issue - Help!

Been struggling with Kinvey’s Angular 2 library since before Ionic 2 RC 0

So far I have tested their library in a JavaScript Angular 2 app, and that works. So I am not pretty sure the problem is either Typings or Rollup (RC0), when using in an Ionic Angular 2 app, which is Typescript

To demonstrate I have forked the Ionic Conference App and made my adjustments as follows

https://github.com/alexbainbridge/ionic-conference-app/commit/e781252521230c822e587f79f90d8ef43ecea4f1

(Note in particular that pulling latest Angular 2 Kinvey library from Git, not from NPM)

They do have a typings file https://github.com/Kinvey/angular2-sdk/blob/master/kinvey.d.ts but I am not clear if it is right. The problem could be on the library as from discussions with them, not sure its fully tested in Typescript yet.

i.e. the problem could be

  • Their end - library (although works in JS Angular 2)
  • Typings
  • Rollup (see RC0 error below)
  • Something else!

[15:34:31] Error: Could not resolve ‘kinvey-angular2-sdk’ from /Applications/MAMP/htdocs/kinvey-angular2-test/.tmp/pages/about/about.js
at Error (native)
at /Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/rollup-plugin-node-resolve/dist/rollup-plugin-node-resolve.cjs.js:78:21
at /Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/browser-resolve/index.js:265:24
at /Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/resolve/lib/async.js:46:14
at process (/Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/resolve/lib/async.js:173:43)
at ondir (/Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/resolve/lib/async.js:188:17)
at load (/Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/resolve/lib/async.js:69:43)
at onex (/Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/resolve/lib/async.js:92:31)
at /Applications/MAMP/htdocs/kinvey-angular2-test/node_modules/resolve/lib/async.js:22:47
at FSReqWrap.oncomplete (fs.js:123:15)

Would massively appreciate if anyone can take a look and see where the problem is

Added it as an issue here