Sorry this was my own stupid fault I should have read the debug properly:

needed to add

import { NgModule, CUSTOM_ELEMENTS_SCHEMA } from ‘@angular/core’;

schemas: [
CUSTOM_ELEMENTS_SCHEMA,
],

to app.module.ts

Thanks for the post, I agree the docs do need desperately updating in terms of support for Angular2 and the cli.

I followed your steps and I managed to get past the ons is undefined error. I can call onsNotification.alert() and that all works great.

However, I cannot seem to create any components as I am now getting
’ons-page is not a known element’

I seem to have loaded everything apart from the components themselves - where there any other steps you followed apart from:

1. npm install -save onsenui angular2-onsenui
2. import { OnsenModule } from ‘angular2-onsenui’; (in app.module.ts)
3. Listing OnsenModule as an import in app.module.ts
4. The steps outlined above

Many Thanks,
Ed

@kasim Did you ever resolve this? I am running into similar issues with OnsNavigator and I’m not sure what I’m doing wrong.

Thanks.