- Read Tutorial
- Watch Guide Video
So, as you're going about and as you're building this, you may have already run into this scenario. And so I'm just gonna make a very quick video just so you know exactly how to handle it.
So, say that you come to the terminal, and you type in expo start, and then you get this big little warning here.
It's a very good idea to make sure whenever you get that, that you follow its instructions and you upgrade the version of the Expo CLI that you're using. That usually is going, there are reasons for it. They usually are adding either security patches, or they might even be adding some new features that are gonna help you build your app in a better way.
So, the fix for this, or the way that you implement it, is actually pretty straight forward. They give you exactly the command that you need to use to run it. So, it says there's a new version of the CLI available. When I'm filming this today, it's 3.154.
And, I will tell you this happens very regularly. I would say almost once a week or so I get this little warning. And so, I wanted to give a guide just so you knew what to do when you saw it. So, you can run this command, and you can either type it out or you can just copy it.
So it's npm install dash g
remember that's because we want this package installed globally, and then expo dash cli
. So, all you have to do is run that command and Node is gonna go up, it's gonna grab that package, and it's going to install it. So, I'm gonna fast forward it, and let's just, I'll come back when it's done.
Okay, it looks like it's been updated. Now, you will see that there's also now a new version of NPM. And the way you upgrade your version of NPM, is to actually run NPM to install it. So, we're gonna copy this npm install dash g npm
. And we'll run this, and I'm gonna do the same thing, I'll just fast forward this as it's installing.
Okay, that's done, and it looks like it all worked. Just a little note, when you're installing packages, it's very natural to see these kinds of warnings and sometimes that can be scary. But the only ones you really need to worry about is when you see a bunch of errors. That usually means that something happened and there's either an issue with the package, there's an issue with your local environment and whenever that happens the best way is really to look at the top error message and then to just google it and see what the fix is. It's usually having to upgrade a version of Node, or something like that.
None of that happened here, but that's just to give you a little bit of a warning because those error messages can be a bit scary. But, you don't have to worry about any of these. These will eventually all be fixed, when either these packages get upgraded, or Expo gets updated again. Each time you install it and upgrade it you're gonna see these types of warnings.
So, just to make sure everything is working, I'm gonna type expo start, and now we should not see any of those warnings. Everything should just boot up, and it looks like it did. I'll bring that window over here. Looks like everything is working. And just to verify it, let's start up and run our iOS simulator. And obviously if you're not using the simulator, if you're on Windows, take a picture of that and then you're gonna be able to see the application on your phone.
So, it looks like all of the upgrades, they didn't have any errors or anything like that cause it appears to be booting up normally. There's our simulator, and Expo is opening up, and everything appears to be working. One other note, this is a little bit of a break for you, cause you're not having to do any code throughout this guide, just a little note, the JavaScript bundle process sometimes this can take a lot longer if you're on a slower internet connection.
My connection here at the studio is not too bad, so it usually boots up pretty fast. But I have done things like work from coffee shops and some spots that had some very poor cell signal and it took a while for that to load up. But it looks like everything here is working, so I think we're good to go, and we're gonna move on to our next guide.