Ionic CLI 4 and ionic-v1 apps - anyone tested?

#1

So I know this is probably like asking if anyone has tested if a rotary phone will be able to navigate a new alexa enabled IVR, but I need to ask:

I have an ionic-v1 project with many cordova plugins. I got a notification that the CLI has been updated to 4.0 (probably to align with the core beta framework release of 4 beta). I am currently on 3.20.0.

I usually like updating (like shiny new things) but don’t want to spend a full day after that trying to figure out why I can’t compile anymore. All this npm/nodejs/foo scares me in general ,but Ionic 4 seems to be a big change in terms of components/approach. Once broken, it takes me a wasted day to reset.

So anyone tried cli 4 with an ionic-v1 project ?

#2

I have a few ionic 3 projects and ran the update today when it popped up during a new build.

As soon as the update was finished I couldn’t run any ‘ionic ’ including ‘ionic info’. It gave me some error about the command not being found in a node_modules directory so I npm uninstalled and reverted to 3.20.0 and now it’s building fine again.

I know this isn’t exactly what you asked since I don’t use ionic v1, but my recommendation based on my attempted upgrade this afternoon is to wait if you don’t like to fiddle around a bit!

#3

Ionic CLI 4 has, as usual, not too much to do with Ionic Framework 4. You should be totally fine upgrading the CLI and keep working on your v1 projects. If something goes wrong, upgrading and if necessary downgrading doesn’t have any effect on your project itself.

#4

Thank you! Exactly what I feared and expected.

#5

This sounds more like an issue with your npm installation to be honest, something to do with permissions and files. This happens quite often and is almost impossible to successfully debug (at least here in the forum).

One solution: Uninstall your node, install nvm (or nvm-windows if you are on Windows), install a new node (which includes npm) with this, then install ionic and cordova again and try your command again.

2 Likes
#6

I actually use nvm and the error pointed to a node modules folder inside a user/my username/library/.nvm directory if I remember correctly.

I figured that I would try to debug it later and downgraded so that I could focus on pushing out an update. I generally try to upgrade dependencies when I need a break for an afternoon, so I’ll dive back in sometime later when I get a chance!

1 Like