Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteTo run an Angular CLI app locally, open a terminal in its workspace and run ng serve. The command builds the app for development, starts a local server—by default at http://localhost:4200/—and rebuilds and reloads the page as you change code. Press Ctrl+C to stop it.
What ng serve does
Angular’s documentation, “Serving Angular apps for development,” says: “You can serve your Angular CLI application with the ng serve command.” The command runs the workspace project’s configured serve target. If you omit the project name, the CLI uses the workspace’s default project. It compiles the app, starts a development server, and watches for code changes so it can rebuild and live reload.
The command can also be written as ng dev or ng s. Run it from an Angular CLI workspace, typically the directory containing angular.json. If the command is unavailable, confirm that you are in the workspace and that its dependencies are installed.
Run the app and choose local server options
Start with:
ng serveThe current Angular CLI reference lists localhost as the default host and 4200 as the default port. Useful options include:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
| Need | Option | Example |
|---|---|---|
| Use a different port | --port |
ng serve --port 4300 |
| Set the host interface | --host |
ng serve --host 0.0.0.0 |
| Open the app in a browser | --open |
ng serve --open |
| Enable or disable file watching | --watch |
ng serve --watch=false |
| Control live reload | --live-reload |
ng serve --live-reload=false |
| Enable hot module replacement | --hmr |
ng serve --hmr |
| Select a named configuration | --configuration |
ng serve --configuration development |
| Load an API proxy file | --proxy-config |
ng serve --proxy-config proxy.conf.json |
| Use HTTPS | --ssl |
ng serve --ssl |
The current CLI reference lists watching and live reload as enabled by default, with HMR defaulting to the live-reload setting. Options and defaults can differ between CLI versions, so check the installed version’s help with ng serve --help.
Check the project’s serve target
The behavior of ng serve comes from the project’s serve target in angular.json. Look under projects, select the relevant project, then inspect architect.serve (some workspace files use targets). The target identifies a builder and can define options and named configurations; it can also reference a particular build target.
@angular/build:dev-server is the common builder in current Angular projects. Older or migrated workspaces may instead use @angular-devkit/build-angular:dev-server. Do not assume every workspace has the same behavior: the configured builder and its version matter, especially for proxy rules and HMR.
Connect the app to a local API
A development proxy lets browser requests to an app-relative path such as /api be forwarded to a local backend, avoiding the need to hard-code the backend host into each request. Angular’s proxy example routes requests to http://localhost:3000.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsRank #3
- Create a proxy configuration file, for example
proxy.conf.json:
{
"/api/**": {
"target": "http://localhost:3000",
"secure": false
}
}- Either add
"proxyConfig": "proxy.conf.json"to the project’sserveoptions inangular.json, or pass the file when starting the server:
ng serve --proxy-config proxy.conf.json- Have the Angular app call a relative URL such as
/api/users. Start the backend separately, then test the request through the Angular app. - If you edit the proxy configuration while the server is running, stop and restart
ng serve; the changed proxy file is not applied until restart.
Proxy path matching depends on the builder
For the Vite-based @angular/build:dev-server, the patterns differ in scope: /api matches only the base path, /api/* matches one path segment, and /api/** matches nested paths. For the Webpack-based @angular-devkit/build-angular:dev-server, /api matches the base route and its subpaths. A proxy rule that worked before a builder migration may therefore need adjustment.
Development serving is not production deployment
ng serve uses the development configuration by default. Angular’s development configuration can include checks, detailed errors, and debugging helpers. Use the development server for local iteration; it is not the command for generating deployable production output.
For a production build, run:
ng buildAngular documents that ng build uses the production configuration by default and removes development-only code from the output. A project’s angular.json can define or override configurations, so inspect its build and serve targets when the behavior differs from these defaults.
Keep secrets out of environment files
Angular environment files can select client-visible settings such as an API base URL for different configurations. Their contents are bundled into the browser application and can be seen by anyone who loads it. Do not put API keys, passwords, or other secrets in them. Keep secrets on a server, and have the app make requests through a backend or another server-side secrets-management approach.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When to use HMR
The current CLI reference exposes --hmr, and its default follows the live-reload setting. HMR behavior depends on the builder and Angular CLI generation. Angular’s build-system migration documentation describes hot replacement of component templates and styles in its documented build-system workflow; do not assume identical HMR support in every older workspace. If ordinary live reload meets your needs, no HMR option is required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
