Dear GOD I just want to revert to v2!


#1

Upgrading to v3 screwed up too much stuff.
How the heck can I get back to the previous versions of ionic/angular/native core needed for my project?
I’ve already repaired the package.json and removed the BrowserModule…
How do I go back on the CLI etc?


#2

It took me about 3 hours to fix everything when I upgraded. Read threads here and on GitHub, and do the tweaks. There isn’t really any going back. Too many bug fixes and performance improvements in Angular 4.


#3

So there’s no way to revert my project/environment to the point it was at 24 hours ago? It worked then…


#4

I don’t really know what’s going on here, but there is absolutely no need to use the prerelease v3 CLI.


#5

Yes @scottmotion, sorry if I wasn’t clear. I’m using Framework 3.0.1 and CLI 2.2.2. That was the 3 hour upgrade.The point is that Angular 4 is a lot better than Angular 2.x. Some people here were running Angular 4 on Ionic 2.something, and I don’t think they reported problems, but it’s not officially recommended by the framework. So moving to Ionic 3 was worth it to me.


#6

Can I please get a moratorium on this phrase? It doesn’t mean anything, and causes so much confusion. It encourages people to install prerelease software (i.e. the CLI) that they really shouldn’t.


#7

Framework 3.0.1? I’m fine with that, if that’s what you’re saying. I was confused for a long time by the name Ionic, because it sounds like one thing. It was a gradual process to learn what app-scripts, webpack, etc., all were. But maybe you’re saying that at least for now it would help to make a strong distinction between framework and CLI?


#8

Precisely, especially because (judging from the volume of bug reports and frantic forum posts) v3 CLI is not ready for prime time.


#9

I have to admit I’m not sure what i’m referring to as “v3” but I followed this: https://github.com/driftyco/ionic/blob/master/CHANGELOG.md
and that’s when it got wonky.

Just trying to undo this if possible…


#10

@AaronSterling I think persistence and rallies of uninstall/reinstall finally won out. Things are looking mostly in order besides AngularFire2, I think…

ionic info:

Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.3
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.10.2
Xcode version: Not installed

package.json snippet:

“dependencies”: {
"@angular/common": “4.0.0”,
"@angular/compiler": “4.0.0”,
"@angular/compiler-cli": “4.0.0”,
"@angular/core": “4.0.0”,
"@angular/forms": “4.0.0”,
"@angular/http": “4.0.0”,
"@angular/platform-browser": “4.0.0”,
"@angular/platform-browser-dynamic": “4.0.0”,
"@ionic-native/core": “3.4.2”,
"@ionic-native/splash-screen": “3.4.2”,
"@ionic-native/status-bar": “3.4.2”,
"@ionic/storage": “2.0.1”,
“angularfire2”: “^2.0.0-beta.8”,
“firebase”: “^3.8.0”,
“ionic-angular”: “3.0.1”,
“ionicons”: “3.0.0”,
“rxjs”: “5.1.1”,
“sw-toolbox”: “3.4.0”,
“zone.js”: “^0.8.4”
},
“devDependencies”: {
"@angular/cli": “^1.0.0”,
"@ionic/app-scripts": “1.3.0”,
“typescript”: “~2.2.1”
},
“cordovaPlugins”: [
“cordova-plugin-whitelist”,
“cordova-plugin-console”,
“cordova-plugin-statusbar”,
“cordova-plugin-device”,
“cordova-plugin-splashscreen”,
“ionic-plugin-keyboard”
],

warnings:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})
npm WARN angularfire2@2.0.0-beta.8 requires a peer of @angular/common@^2.0.0 but none was installed.
npm WARN angularfire2@2.0.0-beta.8 requires a peer of @angular/compiler@^2.0.0 but none was installed.
npm WARN angularfire2@2.0.0-beta.8 requires a peer of @angular/core@^2.0.0 but none was installed.
npm WARN angularfire2@2.0.0-beta.8 requires a peer of @angular/platform-browser@^2.0.0 but none was installed.
npm WARN angularfire2@2.0.0-beta.8 requires a peer of @angular/platform-browser-dynamic@^2.0.0 but none was installed.


#11

Just revert your changes and go back to the last Git commit before you started changing stuff.

You are using Git, right?


#12

I tried that Sujan12 but was unable to revert. Just started programming about 2 months ago and I have had nothing but trouble reverting with Git, there’s always conflicts. Looks like I’ve resolved everything but the current known Firebase/Angularfire2 issue. I think it came down to uninstalling/reinstalling but I couldn’t replicate the process even if I wanted to. Thanks for the support though!


#13

With the right GUI using git is no problem at all (I use Sourcetree from Atlassian as I host most stuff on Bitbucket). Take some time to find one that suits your needs, you will need it a few more time :wink:


#14

IntelliJ IDEA also has great builtin git support.


#15

I went with GitHub thinking it would be a “fool-proof” solution. How wrong I was!
In hindsight I had absolutely no idea how git worked. I figured you just click revert and WHAM! its all back to the previous “save point”. Of course now i’ve learned about git bash and how to resolve the conflicts…

In the end I think my answers are these:
1: start a new project and import my existing code.
2: “git better” (insert pun here)

:slight_smile:


#16

Actually, you can do it exactly this way: Delete old checkout, check out old commit that worked fine.
Continuing development is another story then :wink:


#17

The way I go about it is usually just:

  1. git branch version-port
  2. git checkout version-port
  3. update the version, update the node modules, fix the errors, migrate the code
  4. git commit
  5. git checkout dev
  6. git merge version-port

This way if something goes wrong just abandon the version-port branch and rollback to the dev branch.


#18

Same thing with me, guides didn’t help and now stuck with white-screen ^^


#19

If one was to update the Ionic CLI, would generating a new project result in a new Ionic 3.x project, or a 2.x project?


#20

You can only generate (you mean ionic start, right?) new projects with the current version.
But if you can get your hands on a “virgin” 2.x project, you can just continue developing this. The used Ionic Framework version is defined by the ionic-angular entry in your package.json.