@rcpinheiro Thanks I tried this and it works. My mistake is that I copied the whole project to www, I should have copied only the files under the dist folder (after running ‘npm run build’ in onsen)

The problem was that the kitchensink project doesn’t include cordova.js as it is made for browsers. The back button problem was solved by simply including “<script src=”./components/loader.js"></script>" in my index.html

Thanks for the info Fran. At the beginning I did stack a tabnavigator inside a navigator and it did work, but I wanted to separate both components (lets say a ‘slides’ component and ‘main app’ component) so logged users automatically skips ‘slides’. ‘Main app’ holds three other components which are loaded as tab pages, and they have deeper levels (like chat/123/) so I thought I could create a route like ‘slides/’. Is it posible to do something like… ‘Slides’ been a ons-navigator and somehow push user to another not related navigator? I will upload my code to github in a few hours so you may get a better idea and tell me a better approach to what I want. Thank you, have a nice day.

@Fran-Diox thanks for your answer.

@denious I see, thanks for sharing the end of the story! Yeah, hopefully after this, Webpack is not a black box anymore :stuck_out_tongue:

@jmi23 Nest an ons-navigator inside ons-splitter-content and call navigator methods instead of splitter’s load. Example in the tutorial.

Very cool knowledge, Fran, thanks for the insight!

Very intresting info thx for this!

Sorry, my Monaca CLI version was 2.1.7 I’ve already updated it and it’s ok. Thanks

@SalamHiyali More info in the previous post. Almost everything is already implemented in this alpha version. We just want Vue developers’ feedback about the API before releasing beta.

@inspirity Here you go :)

Does it mean you can use Polymer Webcomponents as well?