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.

The Siget project ships with Angular’s built-in development server, powered by the @angular/build:dev-server builder. It provides fast incremental rebuilds, hot module replacement, and detailed error overlays — everything you need to iterate quickly without any extra configuration.

​
Starting the Server

The simplest way to start the server is to run either of the following commands from the project root: 
npm start
# or equivalently
ng serve
The server compiles the application, begins listening on http://localhost:4200, and automatically reloads the browser whenever a source file changes. You do not need to restart the process between edits.

​
Serve Configuration in angular.json

Siget’s angular.json wires the serve architect target to @angular/build:dev-server and maps each named configuration to the corresponding build target: 
"serve": {
  "builder": "@angular/build:dev-server",
  "configurations": {
    "production": {
      "buildTarget": "siget:build:production"
    },
    "development": {
      "buildTarget": "siget:build:development"
    }
  },
  "defaultConfiguration": "development"
}
The defaultConfiguration is development, so a plain ng serve always starts in development mode. Passing --configuration production switches it to the production build target.

​
Common Flags

FlagDefaultDescription
--port4200Port to listen on
--hostlocalhostHost to bind
--openfalseOpens the browser automatically after the build succeeds
--configurationdevelopmentBuild configuration to use (development or production)

​
Examples

# Start on a custom port
ng serve --port 3000

# Start and open the browser automatically
ng serve --open

# Start using the production build configuration
ng serve --configuration production

​
Development vs. Production Mode

The development and production build configurations differ in several important ways. Siget’s angular.json defines them explicitly under the build architect target: 
"configurations": {
  "production": {
    "budgets": [
      { "type": "initial", "maximumWarning": "500kB", "maximumError": "1MB" },
      { "type": "anyComponentStyle", "maximumWarning": "4kB", "maximumError": "8kB" }
    ],
    "outputHashing": "all"
  },
  "development": {
    "optimization": false,
    "extractLicenses": false,
    "sourceMap": true
  }
}
AspectDevelopmentProduction
OptimizationOffOn (minification, tree-shaking)
Source mapsEnabledDisabled by default
Output hashingOffAll files hashed
License extractionOffOn
Bundle size budgetsNot enforcedEnforced with warning/error thresholds
Running ng serve --configuration production is useful for catching budget violations or testing the optimized bundle locally before deploying.
Once the server starts, your application is available at http://localhost:4200. The terminal will display the exact URL and confirm when the build is ready.
Add the --open flag to have the Angular CLI automatically launch your default browser as soon as the initial build finishes: ng serve --open.

Build docs developers (and LLMs) love

Get started for freeTalk to us