1.6 CLI Options
The CLI supports a wide range of options that can be configured, so in this lesson we'll take a quick look at these.
1.Introduction6 lessons, 42:00
2.Get Started With Angular7 lessons, 42:38
3.Core Concepts7 lessons, 55:20
4.Template Deep Dive11 lessons, 1:10:56
5.Forms10 lessons, 1:45:41
6.Routing9 lessons, 1:15:10
7.Using the HTTP Client5 lessons, 56:24
8.Testing10 lessons, 1:23:27
9.Building for Production1 lesson, 03:40
10.Conclusion1 lesson, 01:32
1.6 CLI Options
Hello folks. In this lesson, we're just gonna take a quick look at some of the different options we have when running commands in the Angular CLI. Back when we initially created the example application, we did use one of these options, the hyphen hyphen style option, which we set to SCSS in order to enable SASS compilation. As well as the style option, we have a whole range of other options that we can make use of. So when scaffolding out an application, the CLI does quite a lot of things for us, such as initializing git in the project directory and adding an initial commit. If we don't want the CLI to do this, we can use either the --skip-git, or the --skip-commit commands, and we would use these like this. And this would tell the CLI not to bother initializing git or creating an initial commit. So you can see in the background in the IDE here, the example application component is separated out into different files. We've got an HTML file which contains the template for the component. We've got the SCSS file, which will contain any styling specific to the component. And we've also got the TypeScript file for the component itself which contains the class that backs the component. So those are all created individually for us by the CLI. Generally, it's useful to have the HTML template and the styling in their own separate files, but we can also choose to have this style and template in line, within the TypeScript file itself instead. If we do want to do that, we can set either the inline-style or the inline-template options to true. And we would do that like this. And then when the test app was scaffolded out, the example app component would just contain a single file, the TypeScript file, and that would contain any styling and the template inline with the file itself. So we specify that the application is gonna be called test-app. And when the CLI scaffolds out the application for us, the folder that it creates the application within will also have this same name, test-app. But we might want to call the app one thing, but put it in a folder called something else. So if we did want to do that, we could use the directory option. So this time the option takes an argument and we specify that using the equal sign after the option, and we just specify the path to the differently named folder that we want the application to be created in. Routing is a very common requirement in bigger, more complex applications, but it isn't used as much in smaller applications, so it isn't enabled by default. We can enable it though, using the routing option, which we set to true if we want to enable routing. In this case when the CLI scaffolded out the application for us, as well as creating an app.module.ts file it would also create a routing.module.ts file which contained all of the client side routing. We will be looking at routing later on in the course. So these are just some of the different options that we can use. If you'd like to see a list of all of the different options that you can use, you can run ng new --help, and that will list all of the different options with a description of how they should be used. So these are all of the different options that we can use when using the new command. There are a number of other commands that we'll be using throughout the course such as the generate command, which is used to generate things like components or services. So if we wanted to see what options we could use with those commands, again, we use the --help. When we use help with the generate command, it tells us the different things that we can generate, and we should also be able to list the different options for each of those different things. So let's say we were generating a component. And again, the output just lists all of the different options that we can use and gives a brief description of those. And it tells us if there's an alias, and that can just mean that we have to type less. So using the help option is a great way to learn how to use the CLI and to get familiar with the many different options. So in this lesson, we looked at some of the different configuration options that we can make use of when scaffolding out a new application to enable or disable different features. We also saw that we can find out exactly which options we can use with any of the different commands using the --help option. Thanks for watching.