Skip to content

Environment setup

Requirements

  • Git
  • Node.js ^20.19.0, ^22.12.0, or ^24.0.0
  • npm (bundled with Node)
  • Python 3 for MkDocs
  • A current Chromium, Firefox, or Safari browser

Confirm versions:

node --version
npm --version
python3 --version

Application

cd basics-components
npm install
npm start

In a second terminal:

cd basics-components
npm test
npm run build

The application defaults to http://localhost:4200.

Documentation

From the repository root:

python3 -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements-docs.txt
mkdocs serve

Windows PowerShell activation is .venv\Scripts\Activate.ps1. MkDocs defaults to http://localhost:8000; the app's Course docs link expects that address during local learning.

Establish a baseline

Before Lesson 1:

  1. Run the build and tests without changing dependencies.
  2. Open the dashboard and inspect the route chunks and console.
  3. Complete the adaptive diagnostic one question at a time.
  4. Create an evidence table from the learning map.
  5. Select a gap, fragile skill, or solid-skill verification from the roadmap.

Do not automatically begin with Lesson 1. Experienced engineers should verify known material and spend time at the edge of current ability.

Setup failure diagnostic

Record these facts before changing dependencies:

node --version
npm --version
npm ls @angular/core @angular/cli typescript
npm run build

Treat compiler errors as evidence

Read the first strict-template error fully before editing. Identify the belief it contradicts—possibly undefined data, incorrect event narrowing, inaccessible members, or invalid binding—then predict why the proposed fix should work.