 As promised, I told you we get to the package JSON file. Now there's a lot to know about a package JSON file, so I want you to know where to get help. Again, it's NPM help. So you type NPM help package JSON and you get this great document on all the things you need to know about package JSON. It literally says this document is all you need to know about what's required in your package JSON file. Now to read through all of this would be incredibly tedious. It's a pretty long document, but when you need it, it will be there. I'm gonna cheat and teach you the NPM init command. NPM init is a way of generating package JSON files and it'll ask you a bunch of questions. So we'll type NPM init and this is short, so let's just read through this. This utility will walk you through creating a package JSON file. It only covers the most common items and tries to guess sensible defaults. See NPM help JSON for definitive documentation on these fields and exactly what they do. Use NPM install package afterwards to install a package and save it as a dependency in the package JSON file. Hit control C at any time to quit. So if you don't like your answers or you feel like you messed up, you can just hit control C and get out of it. So let's start. Package name, essential NPM is the suggestion. That sounds great. It's asking if we wanna start with version 1.0.0. Sure, that's fine. Description, essential, react examples. The entry file is just gonna be our main JavaScript file. So index.js is fine for now. We can change this later. We don't have any tests so we can just enter on this one to skip it. We don't have a git repository. If this was already a git repository, it might be able to pull that information in. Keywords are just ways for someone to find this in search results. We don't need to worry about that right now. The author is me, Michael Chan, and the license. If you have a preference on license, you can use that. Maybe it's MIT or something like that or you can just take the default. Awesome. So it's about to write our package JSON file. That's great. And it's giving us a look at what it looks like. All our information is correct. So we'll just hit enter again and see what we got. I like to use the cat command if I want to just output a file. From here, you could edit it further if you wanted. But I think we're good. So now that we have our package JSON file, let's try installing a package. Since this site mostly focuses on react, I'll install react. NPM install react. We've got a warning that there was no repository field. That's correct. We did not add that. Again, it's just a warning, no problem. React was added as well as the 17 packages it depends on. You'll note it also removed the eight packages that I guess we just didn't need anymore. So that's cool. Let's see what our dependency graph looks like now with NPM LS. Our only direct dependency is react and then there's a bunch of things that it depends on. Cool. Now that we have a package JSON file, let's see if it was updated. Awesome. With our package JSON file in place, it added this react as a dependency. In the next lesson, we'll talk about why that is important and super awesome.