rollup - pretty straight forward - works good.
What stinks is scripts part - today I was reading scripts source in order to find how to subscribe / extend to files watcher and I can say I’m close 
Definitely gulp makes more sense to me - at the end we’ll end up with BASH 
The thing is i have been using webpack since alpha.43 or so, so my project is basically binded to webpack, if the npm scripts trigger rollup then we need a version for webpack, right? just like the gulp one had scripts for webpack with ionic-gulp-webpack.
I think you would be interested in following ionic-app-scripts #16.
I only have 11 components and a boot time of around 10 seconds. My app is relatively simple just a few form fields per page. I’ve never seen lag from page to page but my startup time is terrible. I noticed no improvement moving to RC0 which involved me creating a whole new project and moving my pages into the new structure.
Is there something I need to do to enable these new performance boosts? Is it the Cordova plugins that definitively add startup time? I’m using the default ones that came with a blank project:
“cordovaPlugins”: [
“cordova-plugin-device”,
“cordova-plugin-console”,
“cordova-plugin-whitelist”,
“cordova-plugin-splashscreen”,
“cordova-plugin-statusbar”,
“ionic-plugin-keyboard”
],
MyApp.ts is empty other than a simple menu with 5 pages as well as a slides page.
I’d like to add that my startup time on windows 10 chrome browser is instant… it is Android that takes 10+ seconds.
Have you tried to deploy in production mode? that should allow you to use AoT which is the main improvement over load time and performance in general.
I’m using the following command line for a release:
cordova build --release android
My package.json scripts are as follows: “scripts”: {
“build”: “ionic-app-scripts build”,
“watch”: “ionic-app-scripts watch”,
“serve:before”: “watch”,
“emulate:before”: “build”,
“deploy:before”: “build”,
“build:before”: “build”,
“run:before”: “build”
},
Other than these… I have done thing else. Is there a way that I can get if AoT is working?
Why Cordova if you’re using Ionic?
I was following this guide?
https://ionicframework.com/docs/guide/publishing.html
What should I use?
Hmm aside from the cordova build --release android thing it is as i publish my Android and IOS app versions.
Except i use ionic build --release android && ionic build --release ios, however i still lack to update to RC.0 soooo…
For now try the ionic cli to build, tomorrow i’ll be attempting the update to RC.0 and i’ll be messing with Rollup (from webpack, i’m very sad to let webpack go).
I’m giving it a try now… Upgrading to Rc0 was unusually difficult for me. I hit a few bugs that caused me significant pain until I isolated them. Hopefully I’m in the minority there. Make sure to back up and good luck.
The ionic build has a partial fail… Seems like another bug. It builds the APK but fails to update the manifest. Who knows what else it missed Checkout the strange remark about IOS below:
C:\projects\slo>ionic build --release android
Running ‘build:before’ npm script before build
StudentLoanOptimizer@ build C:\projects\slo
ionic-app-scripts build
[23:55:26] ionic-app-scripts 0.0.23
[23:55:26] build prod started …
[23:55:26] clean started …
[23:55:26] clean finished in 16 ms
[23:55:26] copy started …
[23:55:26] ngc started …
[23:55:26] lint started …
[23:55:26] copy finished in 182 ms
[23:55:27] lint finished in 1.15 s
[23:55:58] ngc finished in 31.57 s
[23:55:58] bundle prod started …
[23:56:12] bundle prod finished in 14.89 s
[23:56:12] sass started …
[23:56:14] sass finished in 1.64 s
[23:56:14] minify started …
[23:56:14] cleancss started …
[23:56:14] uglifyjs started …
[23:56:30] uglifyjs finished in 16.30 s
[23:56:30] cleancss finished in 16.30 s
[23:56:30] minify finished in 16.30 s
[23:56:30] build prod finished in 64.42 s
✗ You cannot run iOS unless you are on Mac OSX.
try ionic build android --release
Haven’t look up any information about this though, but this is the case when I update my NPM and try to build on older beta.11 project I have to put --release tag after ionic build [platform]
Seriously? the ionic cli care about flag order or position?
@keeper3000 Off course i back up, that’s what Git is for, if any developers aren’t using it today then they’re doing it wrong.
Also @danbucholtz in the Ionic team is documenting the issues Rollup has with any given library like for example Moment, Chart.js and a few others that people has reported, at the end of the issue #16 on ionic-app-scripts @danbucholtz posted the uri’s for such docs on Rollup quirks.
It did in my case… I guess they set default to iOS build if no platform defined. In this case platform must be placed after build tag.
Note: this is a beta.11 project, I haven’t tried it on rc.0
Your system information:
Cordova CLI: 6.3.1
Ionic Framework Version: 2.0.0-beta.11
Ionic CLI Version: 2.1.0
Ionic App Lib Version: 2.0.0-beta.20
OS: Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS
Node Version: v4.6.0
my program open 15 sec on android!!! how make the open 3 sec? the ionic beta 11 the best open …
As I already wrote my app with RC.0 take like 6sec on Nexus 5X to start.
Furthermore I could add to that that I’ve got around 100 typescript files/classes of my own in my app and I’m using around 15 cordova plugin including vkwebview and walk and around 10 third node_modules libraries.
The apk is around 27mb.
Thought might be good to compare these facts too.
for Android, my programm open Crosswalk 15-20 sec
@bondraenko @wienzzz it is irrelevant to post for beta11 - try first to migrate to RC0. A lot of performance issues has been solved there.
For sure you can’t expect to have any effort invested on beta11 anymore
I know, that’s why I said old project 
Since the old project is “released” already in my company, I can’t alocate time to migrate it to RC.0 at this moment (after reading lots of documentation and forum about RC.0). on RC0 I only serve it on the web using ionic serve command… haven’t try to build it yet
