1
00:00:01,470 --> 00:00:06,410
So our big problem now is that we can't run Watpac in the browser, are we going to give up now?

2
00:00:06,720 --> 00:00:08,520
We're going to figure out some way of dealing with this.

3
00:00:09,060 --> 00:00:13,410
So just as a very quick reminder, we're going to get some raw code from our user that they type into

4
00:00:13,410 --> 00:00:14,930
a code editor inside that code.

5
00:00:14,940 --> 00:00:20,160
So we've been sailing saying that we wanted to do some trans piling inside the browser, maybe using

6
00:00:20,160 --> 00:00:22,920
Babul, and that does, in fact work inside the browser.

7
00:00:23,220 --> 00:00:27,900
And we would then take that code and do some bundling with WABAC, but that doesn't work in the browser.

8
00:00:28,500 --> 00:00:34,110
So to solve this, we're just going to throw away Battle and Watpac entirely and we're going to rely

9
00:00:34,110 --> 00:00:36,240
upon a different processing tool.

10
00:00:37,000 --> 00:00:40,320
So we're going to use a completely different tool called s built.

11
00:00:40,800 --> 00:00:47,190
Yes, build is a single standalone tool that completely replaces both Babul and WABAC.

12
00:00:47,460 --> 00:00:53,040
It is a single tool that we can safely run inside the browser that can transport JavaScript code and

13
00:00:53,040 --> 00:00:54,840
bundle it at the exact same time.

14
00:00:55,410 --> 00:00:58,410
Let's go take a look at the documentation for s build very quickly.

15
00:00:59,160 --> 00:01:04,349
Inside your browser, you can do a very quick search for E build and the first link should be for the

16
00:01:04,410 --> 00:01:05,129
GitHub page.

17
00:01:06,750 --> 00:01:11,250
Here on the bill to get updates, you can take a look at the documentation on here, can also take a

18
00:01:11,250 --> 00:01:14,250
look at the documentation link, which is on the top right hand side.

19
00:01:14,580 --> 00:01:16,250
Build GitHub IO.

20
00:01:17,390 --> 00:01:21,920
Once you go to the main documentation page, you'll see a chart right away saying that this tool is

21
00:01:21,920 --> 00:01:22,650
really fast.

22
00:01:23,150 --> 00:01:25,060
This chart right here is no joke.

23
00:01:25,070 --> 00:01:25,930
It is not a lie.

24
00:01:26,390 --> 00:01:30,980
I originally implemented this entire application using weapons and then eventually replaced it with

25
00:01:30,980 --> 00:01:31,670
SS built.

26
00:01:32,330 --> 00:01:36,590
Going from way to build was a very significant speed-up.

27
00:01:37,020 --> 00:01:43,160
We're going to be able to transport and bundle users code and immediately executed in ridiculous speeds

28
00:01:43,160 --> 00:01:44,990
just almost instantaneously.

29
00:01:46,220 --> 00:01:51,560
If we were to implement our application using Watpac, if a user tried to import a couple of different

30
00:01:51,560 --> 00:01:55,820
modules, it would potentially take us several different seconds or several seconds to actually bundle

31
00:01:55,820 --> 00:02:00,230
the user's code with all the different dependencies that they might try to import with us built.

32
00:02:00,230 --> 00:02:02,610
This entire process will occur almost instantly.

33
00:02:03,080 --> 00:02:05,180
So this really is a fantastic tool.

34
00:02:05,180 --> 00:02:08,720
And like I said, it's going to be the absolute linchpin of our application.

35
00:02:09,620 --> 00:02:13,910
So the remainder of this course, or I should say the remainder of this section, we're going to spend

36
00:02:13,910 --> 00:02:18,710
a decent amount of time working with Eskild and kind of building a prototype for our daybook application,

37
00:02:19,010 --> 00:02:24,620
making sure that we can take some arbitrary code, trans pilot, bundle it and then get some actual

38
00:02:24,620 --> 00:02:27,520
result that we can then execute on that topic.

39
00:02:27,530 --> 00:02:30,380
Do you remember we still have one small outstanding problem.

40
00:02:30,660 --> 00:02:34,340
We do still have to take a look at how we're going to actually execute the user's code.

41
00:02:34,730 --> 00:02:35,960
Don't forget, we still have to do that.

42
00:02:36,200 --> 00:02:40,130
But right now, we're going to spend some time with us, build and figure out how to use it to both

43
00:02:40,280 --> 00:02:42,760
transpire and bundle our users code.

44
00:02:43,550 --> 00:02:44,660
So that's what's coming up.

45
00:02:44,840 --> 00:02:47,810
Let's take a pause right here and start writing some code in just a moment.