Onto our next step, we have to make sure that if we are building a Seelie in this case, we are we
need to configure the file that we want to run whenever a user tries to run our package from the terminal.
So this will be identical to what we did just a moment ago, back inside of that tiny deployed package
we put together.
I'm going to find my Seelie package just on file anywhere inside if you're going to add in a bin section.
So whenever someone runs our package from the command line, we're going to try to execute our dist
index, not just file, but in here dist index dojos.
We also need to make sure that we add in that very distinctive little comment inside of our SAAC index
not to file as well.
But the very top of this one.
We can add in lb exclamation usar bean ENB note like so.
OK, simple enough.
Now on to adding a pre published and technically it's a pre publish only script, just to be really
precise.
So let's go through all of our different packages and add that in very quickly, for the most part,
going to be very easy and straightforward, but there's one little exception.
We'll take care of.
They'll begin first with Elai, I'm going to find my package not just on file.
Inside of my script section, I'm going to add in a.
We publish only script.
And whenever we run the script right here, or really NPM runs it for us automatically, all we have
to do once again run the typescript compiler.
That's it.
Camping with local API instead of local will find the package JSON file.
I'm going to remove the test script, which we are not using at all.
And replace it with print publish only.
And again, all I want to do is run.
And then finally, inside of local client, we'll find package, Jason.
And then in this case, if we find our script section down towards the bottom, there already is a built
command so we can add in our own free publish only and then have that just run and run.
Billed as a quick reminder, thanks to a very small bug inside of our markdown library, that we are
using this react in the editor.
It does take a pretty long time for us to build up our local client project.
When we go to publish everything, just just make sure it's very clear.
It will take you several minutes all the way up to 10 minutes plus to build the local client project
in just a very quick reminder there.
OK, this looks good.
Now onto our last step, which we will take care of in the next video we are going to commit to get,
but before we actually do that, there's one other just very small item I want to remind you about.
Remember, we had said a long time ago inside of our Seelie Service Command file.
Remember, we have this is a production flag right here, and I told you that we were going to write
a script to replace this process of note envy at build time with a string of production.
So in other words, we're going to go into this code file and more or less replace that with a string
of production.
And that was specifically when we were trying to deploy this package.
We never actually got around to that.
And it kind of seems like since in this video we are addressing writing some kind of build scripts inside
of your seems like this is probably the time to handle that and just make sure it gets taken care of
correctly.
So rather than committing to get as we would normally do in just a moment, we're going to instead do
a very quick another side to make sure that we do that little script to replace processing and be right
there with that string.
Let's take care of that in just a moment.