Sure. But the build process is still about 15-20 s with RC1 compared to 3-5 s with beta.
As for the moving back to webpac… I wish you (and us) a wise and quick decision. Please keep the decision process as transparent as possible. We have to know what we will face in the next weeks/months.
Which command can I use to roll back? Thanks!
For starters, should they start using RC-1 or beta-11?
If you just started, rather RC
Does anyone know what is the command to install beta 11?
npm install ionic@??? -g
Can someone confirm this? npm install ionic@2.1.0-beta.3 -g
You will have a hard time rolling back. I suggest deleting all of your stack even node. Clean it all out. Then install with the command you have given, but make it
npm install ionic@2.0.0-beta.11
On the other hand…
I solved all problems, it’s possible, guys. It was an insane Sprint, I went everywhere with my laptop. We had 3 branches racing against each other. I locked down our main branch. I put in 24/7 for 10 days. I fixed 200 bugs. Tomorrow will be mega merge day.
So - It’s possible and i must say 50% were our own bugs and NGC helped us find them but 50% were undocumented or hard to research and debug ng2 and ionic rc0 upgrades. Hang in there, you can do it, too!
Finally, spending lots of time migrating beta 11 to rc0. Now it works! Super fast… !
I dont know if all of you face 25 seconds for code changes. Rollup has made me lazier and frustrated on the other hand.
Hi, yes same for me with rollup, every change take up to 1min. But in the next ionic release (?), webpack should be back (as an option), as said by Max here ‘rolling back to webpack’.
I recently started creating an Ionic1 project. Without previous knowledge I had a small working app in 2 days. Super nice, super fast. Now I spent more than 50 hours trying to convert this to Ionic2 (rc1) and it gave me so much issues I decided to abandon it and go back to the Ionic1 code. (Black/white screens, or even half of the screen black, layout issues an Android, app icon wrong, all the code issues with Typescript, it’s slower,…) It’s really frustrating since Ionic2 gives a lot of nice features, but it doesn’t appear to be stable enough.
Is this a rant? maybe yes, but it’s meant as a counterweight to all the posts convincing me to switch to Ionic2 as fast as possible 
Ionic is great and I hope Ionic2 will soon be mature enough so I can migrate again.
To be honest, I think that you could wait more to have the feeling that Ionic2 will be more mature, but at the end, you will have again to spend these hours to migrate your project.
Angular2 is fully different than Angular1, for the good in my point of view, the time to invest to migrate there won’t change.
Futhermore, if you don’t already use typescript in your project, the time to migrate your javascript code to typescript will also be there again.
I’m agree, maybe with some maturity the build scripts gonna be more performant and some bugs (which actually may need some work around) gonna be solved, but that wasn’t maybe the most time consuming part of the migration.
And bigger your app gonna be, bigger your migration time gonna be.
P.S.: I’m just trying to motivate you to go on with Ionic2
I have the problem that I currently already spend literal days trying to update to an RC version.
I’ve been using webpack since start because I need certain functionality which I can’t create in ionic itself (Different stylesheets / Pages based on config etc.).
now I can’t get my webpack config to work, I’ve tried just updating dependencies, I’ve tried using the scripts recently introduced. ANd I just keep getting annoying errors. At the moment nothing seems resolveable the paths all fail, no clue why.
