1
00:00:01,240 --> 00:00:06,100
It's time for us to finally deploy our application off to NPM so that a user can install our Seelie

2
00:00:06,100 --> 00:00:09,210
package onto their local machine and run the JDBC app.

3
00:00:09,710 --> 00:00:12,640
Those take a look at a couple of diagrams and understand how we're going to do this.

4
00:00:13,520 --> 00:00:18,170
So at present, you and I have these three packages on our local machine, we need to figure out some

5
00:00:18,170 --> 00:00:20,810
way to publish all three off to the NPM registry.

6
00:00:21,260 --> 00:00:25,220
And remember, all these different packages have little dependencies between them.

7
00:00:25,560 --> 00:00:29,870
So, for example, the Seelie depends upon local API to work correctly.

8
00:00:30,980 --> 00:00:36,890
And the local AP depends upon local client to work correctly, so all three of these different packages

9
00:00:36,890 --> 00:00:38,960
are somewhat linked in some way.

10
00:00:40,060 --> 00:00:44,860
Once we've deployed all these to the history, we then want to allow a user to run the command like

11
00:00:44,860 --> 00:00:50,920
NPM, install DAG JDBC or something very similar to that, that should then download all the source

12
00:00:50,920 --> 00:00:59,210
code for the supply and the depend upon local API and the depended upon local client onto a user's machine.

13
00:00:59,920 --> 00:01:02,410
So we should end up with our Seelie on the user's machine.

14
00:01:02,680 --> 00:01:08,410
Inside of that things node modules directory will be our local API and inside of that node modules directory

15
00:01:08,440 --> 00:01:09,730
will be our local client.

16
00:01:11,250 --> 00:01:16,980
Now, this entire process of just pushing a package off to NPM is already just a little bit complicated,

17
00:01:17,220 --> 00:01:22,200
but we are now also saying that we need to push off three different packages and they are somehow linked

18
00:01:22,200 --> 00:01:26,460
together in some way to just make our lives a little bit easier.

19
00:01:26,490 --> 00:01:30,450
We're going to go through a very, very quick and very small side project together.

20
00:01:30,910 --> 00:01:34,910
We are going to create a very small package called Ayni NPM Deploy.

21
00:01:35,550 --> 00:01:39,420
We're going to walk through the entire process of setting up an environment very similar to what we

22
00:01:39,420 --> 00:01:40,560
are doing inside of our Seelie.

23
00:01:40,870 --> 00:01:45,000
We're going to make sure that we can write out some typescript and file that type script into JavaScript,

24
00:01:45,330 --> 00:01:50,910
then eventually push the result off to the registry and then eventually install that onto our local

25
00:01:50,910 --> 00:01:55,800
machine and then run it as though it were some kind of command line tool on our local machine.

26
00:01:56,910 --> 00:02:02,220
This might seem like a unnecessary extra step that we're going through here, but trust me, we're going

27
00:02:02,220 --> 00:02:07,020
to run into a lot of very small, interesting issues as we start to publish all of our different packages

28
00:02:07,020 --> 00:02:08,460
off to the NPM registry.

29
00:02:08,850 --> 00:02:12,630
It's really worth the time to just make sure that we are 100 percent on the same page on how all this

30
00:02:12,630 --> 00:02:13,200
stuff works.

31
00:02:13,860 --> 00:02:15,560
So then mind let's take a pause right here.

32
00:02:15,600 --> 00:02:19,380
We'll come back to the next video and we're going to start to do some setup of this separate little

33
00:02:19,380 --> 00:02:24,200
package completely outside of our a project called Tiny and Deploy.