It's time for us to finally deploy our application off to NPM so that a user can install our Seelie
package onto their local machine and run the JDBC app.
Those take a look at a couple of diagrams and understand how we're going to do this.
So at present, you and I have these three packages on our local machine, we need to figure out some
way to publish all three off to the NPM registry.
And remember, all these different packages have little dependencies between them.
So, for example, the Seelie depends upon local API to work correctly.
And the local AP depends upon local client to work correctly, so all three of these different packages
are somewhat linked in some way.
Once we've deployed all these to the history, we then want to allow a user to run the command like
NPM, install DAG JDBC or something very similar to that, that should then download all the source
code for the supply and the depend upon local API and the depended upon local client onto a user's machine.
So we should end up with our Seelie on the user's machine.
Inside of that things node modules directory will be our local API and inside of that node modules directory
will be our local client.
Now, this entire process of just pushing a package off to NPM is already just a little bit complicated,
but we are now also saying that we need to push off three different packages and they are somehow linked
together in some way to just make our lives a little bit easier.
We're going to go through a very, very quick and very small side project together.
We are going to create a very small package called Ayni NPM Deploy.
We're going to walk through the entire process of setting up an environment very similar to what we
are doing inside of our Seelie.
We're going to make sure that we can write out some typescript and file that type script into JavaScript,
then eventually push the result off to the registry and then eventually install that onto our local
machine and then run it as though it were some kind of command line tool on our local machine.
This might seem like a unnecessary extra step that we're going through here, but trust me, we're going
to run into a lot of very small, interesting issues as we start to publish all of our different packages
off to the NPM registry.
It's really worth the time to just make sure that we are 100 percent on the same page on how all this
stuff works.
So then mind let's take a pause right here.
We'll come back to the next video and we're going to start to do some setup of this separate little
package completely outside of our a project called Tiny and Deploy.