My project has started up.
I don't see any distinct areas inside of here or anything like that so I can't go back over my browser
and do a quick test.
I still have my original window open at ticketing dot Dev.
Remember that's how we access our application so I'm going to refresh this and I should still see content
up here.
Looks good.
All right so that definitely means that everything is working as expected.
Now at this point I would like to very quickly show you how we can very easily make a change to something
inside of our common module and then reflect those changes inside of our off project.
Let's imagine that we need to make a change to the common module maybe inside the index TSA file.
Maybe.
I don't know we need to add just a simple comment at the top.
Opening the coming up here that says something like re export stuff from errors and Middleware is simple
enough.
Now if you wanted to get this change reflected or this update over to our auth project here's what we
would do.
We'd save these changes we would go back over to our terminal we would change into our off directory
or not OK.
What common we eventually want to be enough.
Right now we want to be inside a common.
So we're going to rebuild and publish our project.
Recall that we put together a little script to automate that entire process for a real project.
We don't really wanted that script but again for this course it's going to save us a decent amount of
time.
We'll do an NPM run hub that'll do the commit the version the build and then publish
and there we go.
So I'm up to version 1 point 0 9.
Chances are you're not at version 1.0 0 9.
I had to record some of the videos before this several times to get everything kind of working just
right.
And that's why I've got this higher version number here.
So latest version is 1 point 0 9.
We need to make sure that our auth project now uses Version 1.0 0 9 as well.
So we'll change over to r and then all we really have to do is an NPM update SGI ticket slash comment.
And of course you'll replace as free tickets with your organization name so I'll run that
and very quickly we will see.
There we go.
Version 1.0 0 9 now that makes a change as usual to our packages on file.
So if we go back over to scaffolds we're going to see that our image is being rebuilt.
We're going to be installing all of our dependencies again which means that we should be getting at
the latest version of that common module not going to let this just do its thing.
You're really quick.
Just so I can verify that this actually all occurred actually no reason.
Well OK.
There it goes.
It always seems like sometimes it takes forever sometimes it doesn't take any time.
OK.
Simple enough looks like everything's restarting.
But how do we actually know that our container is running the correct version of that dependency.
Well we could actually kind of go into the container and just verify that everything worked as expected.
Let me show you how I can open up another terminal window.
I'm going to do a cube Seitel get pods.
I'm going to find the pod running our authentication project and I'm going to try to start up a shell
inside of that pod.
So we're going to access the container inside there and tried to take a look at some of the different
files inside of that container directly just to make sure we're running the latest version of our common
project.
It's going to copy that pod name and do a cube Seitel exact dash I.T. then the pod name and then SDH
at the very end so I've now got a shell running inside of that container there is the node modules directory
inside there.
So I want to try to open up that node modules folder.
I want to find our common module inside there.
Now I just want to print out the package not just on file and make sure that we got version 1.0 0 9
side there.
So I will change into a node modules.
I'll then change into my organization inside there which is SMG tickets.
Again you'll need to update that organization name inside of there is the common folder.
There's the packages on file and something is kind of interesting that you'll notice when we install
this thing as a dependency.
We didn't get the SRT folder or anything like that.
All we got was the build directory and all the files inside there because remember we had sent that
files property inside of our common modules packages on file.
Now I will cut the package J some file just a printout all the information side there and if I scroll
up a little bit I should be able to verify that I've got version 1.0 0 9.
That means that my container is running the correct version of this module.
The updated version 1.0 night right there OK.
So that's it.
That's how we do an update.
Now of course you don't actually have to go to the process of verifying that package.
It's on file.
All we really have to do is run some changes inside of our common module.
We're going to run that NPM run pub command.
We'll do it in NPM updates inside of our project.
And that's pretty much it.
That's all we have to do.
So it looks pretty good.
We've got this common module that's going to make it really easy to create some additional services
in the future such as the ticketing one they're we're gonna start here in just a second.
And any time we need to make changes to the thing well we've got a strategy for it.
All right enough with lecturing from me I'm kind of rattling on now.
So pause right here.
Let's kick off our ticketing service in the next video.