In the last section we finished a little bit of boilerplate set up inside of our application.
But when we tried to run it from the command line we saw a little bit of an error message.
So I'm currently inside my server directory and if I run NPM run Dev I will immediately start to see
a little error message.
Error messages being emitted by the client side of our application.
The server is still successfully running.
So the server might look A-OK.
You know this is all the server logs right here.
But you may see an error message around the client.
Now this air that we're seeing is really related to the current release version of NPM.
If you're using the same version as I which is 5.0 0.3 you're probably seeing an error message like
this.
But if you're using a new newer version you might not see an error message at all which is totally fine
if you don't see is there a message just pause this video right now and go to the next one.
Otherwise stick around and we're going to fix this thing up.
So fixing that error message is pretty straightforward.
I'm going to kill the running server.
I'm going to change into the client directory.
I'm going to list out all the files inside of here and then you'll find one file called package dash
Lockart Jaison.
I'm going to delete this file.
And so you can either delete it by using your command line or by changing over to the your code editor
and finding that package that Ashlock excuse me file inside of the client directory.
So here's my client directory.
Here's the package that is on file and side of it.
I'm going to just delete that file like so.
OK so now I'm back in the client directory.
I'm still inside the client directory right now.
I no longer have the package dash lock file.
I'll do an NPM install.
And that's pretty much it.
So the NPM install at this point might take a couple of minutes or two if you see some type of warning
message in here that says something like Oh relax.
Peer dependency or was expecting some other version like blah blah or something like that.
That's totally fine.
You can completely ignore it.
Again that error message that we just saw about cannot find scripts start or whatever 100 percent being
Genner by and then right now.
So at this point we're going to just let this thing run its course we'll continue in the next section.
And we're just going to verify that our servers are still working correctly by attempting to run it
again.
So let's let the MPAA install finish and I'll catch you in the next video.