So our big problem now is that we can't run Watpac in the browser, are we going to give up now?
We're going to figure out some way of dealing with this.
So just as a very quick reminder, we're going to get some raw code from our user that they type into
a code editor inside that code.
So we've been sailing saying that we wanted to do some trans piling inside the browser, maybe using
Babul, and that does, in fact work inside the browser.
And we would then take that code and do some bundling with WABAC, but that doesn't work in the browser.
So to solve this, we're just going to throw away Battle and Watpac entirely and we're going to rely
upon a different processing tool.
So we're going to use a completely different tool called s built.
Yes, build is a single standalone tool that completely replaces both Babul and WABAC.
It is a single tool that we can safely run inside the browser that can transport JavaScript code and
bundle it at the exact same time.
Let's go take a look at the documentation for s build very quickly.
Inside your browser, you can do a very quick search for E build and the first link should be for the
GitHub page.
Here on the bill to get updates, you can take a look at the documentation on here, can also take a
look at the documentation link, which is on the top right hand side.
Build GitHub IO.
Once you go to the main documentation page, you'll see a chart right away saying that this tool is
really fast.
This chart right here is no joke.
It is not a lie.
I originally implemented this entire application using weapons and then eventually replaced it with
SS built.
Going from way to build was a very significant speed-up.
We're going to be able to transport and bundle users code and immediately executed in ridiculous speeds
just almost instantaneously.
If we were to implement our application using Watpac, if a user tried to import a couple of different
modules, it would potentially take us several different seconds or several seconds to actually bundle
the user's code with all the different dependencies that they might try to import with us built.
This entire process will occur almost instantly.
So this really is a fantastic tool.
And like I said, it's going to be the absolute linchpin of our application.
So the remainder of this course, or I should say the remainder of this section, we're going to spend
a decent amount of time working with Eskild and kind of building a prototype for our daybook application,
making sure that we can take some arbitrary code, trans pilot, bundle it and then get some actual
result that we can then execute on that topic.
Do you remember we still have one small outstanding problem.
We do still have to take a look at how we're going to actually execute the user's code.
Don't forget, we still have to do that.
But right now, we're going to spend some time with us, build and figure out how to use it to both
transpire and bundle our users code.
So that's what's coming up.
Let's take a pause right here and start writing some code in just a moment.