Hi, @vgriffin .

ERROR Error: No provider for OnsNavigator! appears when the component is not a descendant of <ons-navigator>.

Basically, if you want to access ons-navigator, ons-tabbar, ons-splitter, ons-splitter-content and ons-splitter-side, we recommend you creating a service which stores a reference to each component.

Thank you.

Hi, @vgriffin !

This problem is a bug of Onsen UI Core and related to this issue ticket (OnsenUI/OnsenUI#1926).

You can avoid the problem by
(1) Keep the content of <ons-tab> empty and use icon attribute of <ons-tab>.

<ons-tabbar animation="none">
  <ons-tab [page]="initPageComponent" icon="md-home" label="Init page" active badge="7"></ons-tab>
  <ons-tab [page]="pageAComponent" icon="md-settings" label="Page A"></ons-tab>
  <ons-tab [page]="pageBComponent" icon="md-pizza" label="Page B"></ons-tab>
</ons-tabbar>

or
(2) Put <div class="tabbar__content"></div> and wrap the <ons-tab>s with <div class="tabbar"></div>

<ons-tabbar animation="none">
  <div class="tabbar__content"></div>
  <div class="tabbar">
    <ons-tab [page]="initPageComponent" label="Init page" active badge="7">
      <ons-icon icon="md-home" size="24px"></ons-icon>
    </ons-tab>
    <ons-tab [page]="pageAComponent" label="Page A">
      <ons-icon icon="md-settings" size="24px"></ons-icon>
    </ons-tab>
    <ons-tab [page]="pageBComponent" label="Page B">
      <ons-icon icon="md-pizza" size="24px"></ons-icon>
    </ons-tab>
  </div>
</ons-tabbar>

Thank you.

@vgriffin
That error on Git was already fixed in Onsen UI 2.5.1.
https://github.com/OnsenUI/OnsenUI/commit/60687db5f857adf00aaa2e7b9b94da43d3afe85b#diff-b9cfc7f2cdf78a7f4b91a753d10865a2

But as I mentioned in the previous reply, ngx-onsenui currently depends on Onsen UI 2.3.x.
I will fix this problem as soon as possible. Thank you.

0 frandiox committed to OnsenUI/OnsenUI

chore(polyfills): Change custom-elements dependency location.

Hi, @vgriffin!

You can fix that kind of error by manually running npm install onsenui@~2.3.3 --save.

The fundamental cause of the error is that ngx-onsenui is not yet supporting the latest version of onsenui (2.5.3).
I am working on updating ngx-onsenui now. Thank you.

@Gyorgy-Orban

There seem to be some recent development going on but at the same time many links on the site / documentation are broken.

In terms of the website, it was not available between 6pm~10pm (GMT+0) due to AWS setting. It is fixed now.

@huybn5776
Yes, the current Angular 2+ binding is not compatible with the latest version of Angular and Onsen UI.
Currently we are working on updating the Angular 2+ binding and Monaca CLI.
Thank you for understanding.

The Onsen UI team has been working to provide you with exciting new features at every new release. Behold as here come some more!

Click here to see the original article

Hi, @btx!

This problem is already mentioned in this topic.
If you want to use Onsen UI with Angular CLI, you have to add the following settings into your .angular-cli.json:

      "styles": [
        "../node_modules/onsenui/css/onsen-css-components.css",
        "../node_modules/onsenui/css/onsenui.css"
      ],
      "scripts": [
        "../node_modules/onsenui/js/onsenui.js"
      ],

Currently we are preparing a new version of angular2-onsenui which supports Angular 4 and fixing the contents in onsen.io.
Thank you.

You may recall that 2 months ago (March 14) we released Onsen UI 2.2.0.
Since then we have continuously worked hard to improve Onsen UI according to the feedback we’ve been receiving (e.g. GitHub issues).
That effort culminated in the latest version, 2.2.6.

In this post we’d like to explain what the most recent updates of Onsen UI are all about.

Click here to see the original article

@Shubham-Kaushik
It seems that you are using onsenui@1.3.17, but Onsen UI 1 is no longer supported.
Could you consider using Onsen UI 2?

@Fran-Diox
I found that this error occurred because:

• We are using for-of syntax in util._captureTree (link).
• for-of syntax is transpiled by Babel.
• But babel-plugin-transform-es2015-for-of outputs code with Symbol (link)
  • Symbol is a feature of ES2015, so this might be a bug
• Symbol is supported since Android 5.1 WebView (link).

What we could do is (1) polyfill Symbol or (2) fix babel-plugin-transform-es2015-for-of.