In this section we're going to open up our code editor and explore our newly created Project.
So I'm going to start up my code editor I'm making use of Visual Studio code.
You can use absolutely any code editor you want inside this course so free free to use Adam or sublime
or Eclipse or whatever it might be.
I would not say that any one editor is better than another for working on reac projects.
In addition in this course you and I are not going to ever depend upon some editor specific feature
in order to get through the course.
So again feel free to use absolutely any editor you want.
Once I had my editor open on then going to open up my project directory.
So here's my newly created GSX X folder right here.
Now inside this folder you'll notice that we have a couple of different files and folders.
These are all automatically generated for us when we just made our project.
I want to take a look at some of the different files and folders here and get a better idea of what
they'll do.
All right.
So just a couple of things we'll go over rather quickly.
First off you'll notice the SIRC directory as sarcy stands for source.
If you open up that folder inside of your code editor right now you'll see that there's already a couple
of different files inside of here.
Again these are all automatically generated by Create racked up over time.
You and I are going to add more and more code to this SIRC directory.
In general we're usually going to delete these automatically generated files inside of your just so
you can understand how to set up a re-act project from complete scratch.
Now of course we're still going to use the Create react up kind of framework in general but we will
not use any of the automatically generated code inside of your next directory.
Is the public directory the public directory right here is going to contain different static files an
example of a static file.
Might be an email file that never changes or an image or maybe music or any other thing that we might
want to serve up from our application.
We'll get a better sense of what we use the public directory for throughout this course.
Next is the node model's directory node modules contains all of the different dependencies that were
installed into our project.
So this consists of those 7300 and 82 dependencies that you just saw at your terminal a moment ago.
Every one of these different folders inside of your represents a different dependency.
You can scroll through this list and get a sense that yeah there's a lot of stuff going on inside of
here.
Now in general you and I are never going to have to manually go into the node modules directory.
It just kind of exists here and we don't really worry about it too much.
Next up is the package chase on file.
The package such chase on file right here.
List out all the different dependencies that our project requires.
And it also has a little bit of project configuration side of it.
Over time you and I are going to do several updates to the package that is on file next a very similarly
named file package lock Esan use package lock right here.
This file it records the exact version of all of the dependencies that we installed into our project.
So inside the package lock you'll see this dependency section right here.
And if you scroll down you'll see that there are a tremendous number of records.
Again this consists of the 7500 and 82 different dependencies that we installed into our project.
And then there's the read me file the Rimi file has some directions in it to tell you how to run this
create re-act up generated project.
So if you want to you could definitely take a look at what's inside of your.
But in general I'm going to tell you everything you need to know.
There's one last file inside of your at the get ignore file.
Ignore file is a reference to the get version control system and essentially it lists out the different
files and folders that get should ignore if it's going to be tracking our project and maintaining a
record of all the different changes we're making to our codebase.
Okay.
So that's it.
That's what we get.
By default when we generate a project with Create we act up.
Now let's take a quick pause right here.
When we come back the next section we're going to finally start writing out some code inside of our
S or C directory in getting a better idea of how GSX works.
So quick Balsall I'll see you in just a minute.