Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/kevinrodriguezmorales/siget/llms.txt

Use this file to discover all available pages before exploring further.

Siget is designed to go from zero to a running Angular 21 application as fast as possible. This guide walks through every step — from installing prerequisites to seeing your app live in the browser and running your first unit test with Vitest.

Prerequisites

Before you begin, make sure the following tools are available in your environment:
ToolRecommended VersionNotes
Node.jsLTS (20.x or 22.x)Required to run Angular CLI and npm
npm10.9.0Declared as packageManager in package.json
Angular CLI21.xUsed for serve, build, and test commands
Install the Angular CLI globally if you haven’t already:
npm install -g @angular/cli
Verify your installation:
ng version

Setup

1

Clone the Repository

Clone the Siget repository from GitHub and navigate into the project directory:
git clone https://github.com/kevinrodriguezmorales/siget.git
cd siget
2

Install Dependencies

Install all project dependencies using npm. Siget declares "packageManager": "npm@10.9.0", so npm is the recommended package manager:
npm install
This installs both runtime dependencies (Angular packages, RxJS) and dev dependencies (Angular CLI, Vitest, Prettier, TypeScript).
3

Start the Development Server

Start the local development server using either of these equivalent commands:
npm start
The Angular CLI will compile the application and start a dev server using the @angular/build:dev-server builder. By default it targets the development build configuration, which disables optimization and enables source maps for easier debugging.
The development server supports hot module reloading — any change you save to a source file is instantly reflected in the browser without a full page refresh, preserving application state wherever possible.
4

Open the Application

Once the server is running, open your browser and navigate to:
http://localhost:4200
The Angular CLI always serves the application on http://localhost:4200 by default. If that port is already in use, you can specify an alternative with ng serve --port 4300.
5

Run the Unit Tests

Siget uses Vitest as the test runner, integrated through the @angular/build:unit-test builder. Run the full test suite with:
npm test
Vitest will discover all *.spec.ts files in the project — starting with src/app/app.spec.ts — and report results directly in the terminal.

Available Scripts

All scripts defined in package.json are available via npm:
CommandUnderlying CommandDescription
npm startng serveStart the development server with hot reloading
npm run buildng buildCompile a production-optimized build into dist/
npm run watchng build --watch --configuration developmentRebuild automatically on file changes (dev mode)
npm testng testRun unit tests with Vitest

Code Scaffolding

The Angular CLI can generate new components, directives, pipes, and more using its built-in schematics. Because Siget configures "style": "scss" in angular.json, all generated components will automatically use SCSS:
ng generate component component-name
To see all available schematics:
ng generate --help

Building for Production

To compile an optimized production bundle:
ng build
Build artifacts are output to the dist/ directory. The production configuration enables output hashing for long-term caching and enforces bundle size budgets (500 kB warning, 1 MB error for the initial bundle).
The default build configuration is production. To build with source maps and without optimization, use ng build --configuration development or run npm run watch for a continuous development build.

Build docs developers (and LLMs) love