Overview
This guide walks you through setting up a complete development environment for ScreenPulse, including Node.js, Angular CLI, IDE configuration, and recommended tools.Node.js Setup
ScreenPulse requires Node.js v18.19.1 (LTS) for optimal compatibility with Angular 16.2.12.Install Node.js
- Using Official Installer
- Using nvm (Recommended)
- Using Homebrew (Mac)
- Download Node.js v18.19.1 LTS from nodejs.org
- Run the installer for your operating system
- Verify installation:
Configure npm
Optimize npm for better performance and security:Angular CLI Setup
ScreenPulse uses Angular CLI v16.2.16 for development and build tasks.Install Angular CLI
Install Angular CLI globally:Angular CLI Configuration
Configure Angular CLI for optimal development experience:ScreenPulse’s
angular.json is already configured with optimal build settings. You don’t need to modify it for basic development.IDE Setup
Visual Studio Code (Recommended)
VS Code is the recommended editor for Angular development.Install VS Code
Download from code.visualstudio.comEssential Extensions
ScreenPulse’s.vscode/extensions.json recommends the following extension:
Angular Language Service
Extension ID:
angular.ng-templateProvides:- IntelliSense for Angular templates
- Error checking in HTML templates
- Go to definition for components and directives
- Auto-completion for Angular syntax
VS Code Settings
Create or update.vscode/settings.json in your project:
Other IDEs
WebStorm / IntelliJ IDEA
WebStorm / IntelliJ IDEA
JetBrains IDEs have built-in Angular support:
- Install from jetbrains.com
- Open ScreenPulse project
- Enable Angular plugin (usually enabled by default)
- Configure TypeScript version: Settings → Languages & Frameworks → TypeScript → Use project TypeScript
Vim / Neovim
Vim / Neovim
For Vim users:
- Install coc.nvim
- Install coc-angular:
- Configure coc-settings.json for Angular support
Git Configuration
Configure Git for contributing to ScreenPulse:Environment Variables Overview
ScreenPulse uses TypeScript environment files instead of.env files. These are located in src/environments/:
Development Environment
File:src/environments/environment.development.ts
Production Environment
File:src/environments/environments.production.ts
Angular automatically switches between environment files based on the build configuration. You don’t need to manually change imports.
Accessing Environment Variables
In your Angular components or services:Browser DevTools
Install Browser Extensions
Angular DevTools
Chrome: Install from Chrome Web StoreFirefox: Install from Firefox Add-onsFeatures:
- Component tree inspector
- Change detection profiler
- Injector hierarchy viewer
- Router debugging
Redux DevTools
Useful if you add NgRx or other state management:Chrome: Install from Chrome Web StoreFirefox: Install from Firefox Add-ons
Additional Development Tools
Package Managers
While npm comes with Node.js, you may prefer alternatives:- npm (Default)
- Yarn
- pnpm
Useful Global Tools
Verify Setup
Ensure everything is configured correctly:Test Project
Next Steps
Configuration
Learn how to configure API endpoints and environments
Development Workflow
Master the ScreenPulse development process