I recently updated to the latest ionic for a new project.
I did it globally (npm install -g ionic), and it brought me to ionic 2.2.2
and now, I can’t seem to get back to an older version of ionic to fix it.
When I run npm uninstall -g ionic, it works good and uninstall it.
Then I run npm install -g firstname.lastname@example.org , and after a while it always ends up with error, not installing ionic.
Only npm install -g ionic seems to be working (but it installs the latest version)
I am starting to think, if my ionic serve isn’t broken at all, and my app only gets broken when I built it and put it on my phone, maybe it’s the cordova upgrade that messed it all up ? is that possible ?
( coz the problem appears when I cordova build --release android )
When i check the “last modified” date of my package.json, it seems like it got updated.
However the content is the same as before (I think…)
My main problem is that I never really maintained my package.json file or paid much attention to the versioning. so far updating always happened without issue.
Hi @mhartington, yes I need an older version so that when I build my app it won’t break all over my css and some plugin.
Since I upgraded node / ionic / npm, even if my ionic serve looks the same, the cordova build --release android creates a different sized apk as before, and when I run it on my android most of the css breaks apart.
Indeed it seems to be a node / node-sass version conflicting.
I went back to a node v 4.4.4, and now I can finally npm install -g email@example.com without error.
Now it’s the npm install -g cordova that seems to be stuck since it’s loading for an hour now, but at least it’s a different problem…