Back over to the search function inside of our local API package, it's inside of your recruiting,
our Express app, and as we just discussed, it has three primary purposes.
So we're going to first work on making sure that we can somehow load up our react application inside
the browser.
Now, there's going to be just a little bit challenging because there's really two different scenarios
we need to think about, or in other words, two different ways in which we are going to actually load
up our react app or get that indexed HTML, file an index, not just file back over to the browser.
So scenario number one that we need to think about is when we have actually deployed our daybook application
and some user has installed it onto their local machine as a Seelie.
So we can imagine that a user here might have done an NPM install for our book command line tool.
They then run JDBC serve.
So at that point in time, we need to start up our local API and we need to make sure that a user can
somehow load up our built react files.
The real question here is, where is that coming from, where are we getting these files from?
How are we actually loading them up and sending them back over to the browser?
Before we discuss what the solution here is going to be, one, talk about scenario two, that we need
to think about, one scenario to scenario to let's make sure it actually says to this is when we are
doing active development of our project.
So like you and I are working on our project right now, at some point in time, we probably want to
make changes to our REACT application and then see them update live on the fly inside of our browser.
So in other words, we want to be running our create up, make some changes to our risk components and
immediately see those changes appear.
We still, however, want to be loading up our application through the local API because, remember,
the local API is going to eventually give us that list of cells that we're going to be looking for and
give us the ability to save a list of cells as well.
So our browser in the development environment, like your browser, my browser, we're going to make
a request to our local API and we need to somehow make a request over to our running react app application
that is running our development server.
And we need to somehow get those HTML and JavaScript files, get them back over into the browser.
Normally, of course, whenever we are working on a reactor application, it would just look like this
would just make a request directly from the browser to create racked up.
And we do that all the time by running a great reactor up and going to say localhost or three thousand.
Now, we're kind of saying that we want to have this extra piece in between and we need to make sure
that our local API is going to somehow route requests over, get those development files and then send
them back over to our browser.
So these are the two scenarios we need to think about, we need to come up with a solution that is going
to work in either scenario.
So let's take a pause right here.
Come back and we're going to first begin with addressing scenario number two.