LearnNgTodoList

This project was generated with Angular CLI version 11.2.1.

Directory structure

• Root module stays at app.
• Components at the global level, and landing pages, are at app/components.
• Custom (feature) modules get a directory of its own at app/<module_name>.
• Components, services etc. at a module level get their own directory at the module directory level: app/<module_name>/components or app/<module_name>/services, for example.

Development

• nvm use
• yarn install
• Run yarn exec ng serve or yarn run start for a dev server.
• Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

⚠ Generally, yarn exec should be OK. If passing flags (such as --routing in the case of ng generate module), yarn exec blows. Use npx.

Releasing new versions

Update the changelog and commit it in with the expected version and date of release added in.

Then, use yarn version as follows:

yarn version --minor --message "chore: release %s"

%s refers to the version that will be committed and tagged. Pick from --major, --minor, --patch, and --new-version to automate or specify a particular version.

Code scaffolding

Run yarn exec ng generate component component-name to generate a new component. You can also use yarn exec ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run yarn exec ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run yarn exec ng test to execute the unit tests via Karma.

Running end-to-end tests

Run yarn exec ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use yarn exec ng help or go check out the Angular CLI Overview and Command Reference page.