
Security News
/Research
Popular node-ipc npm Package Infected with Credential Stealer
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.
π A simple background process manager for npm dev commands
devctl is a lightweight command-line tool that runs your npm run dev command in the background and provides simple management commands. Free up your terminal during development while automatically logging all server output.
npm run dev in the background, freeing up your terminal# Global installation (recommended)
npm install -g devctl
# Or install in your project
npm install --save-dev devctl
# Start development server (in background)
devctl start
# Check server status
devctl status
# View real-time logs
devctl logs
# Stop server
devctl stop
# Restart server
devctl restart
| Command | Description |
|---|---|
devctl start | Start npm run dev in background |
devctl stop | Stop the development server |
devctl restart | Restart the development server |
devctl status | Check server running status |
devctl logs | View real-time logs |
Start development server:
devctl start
Example output:
π Starting development server...
β
Development server started!
π Process ID: 12345
π Log file: ./logs/dev.log
Check status:
devctl status
Example output:
β
Development server is running
π Process ID: 12345
π Log file: ./logs/dev.log
π Uptime: 01:23:45
View logs:
devctl logs
This will display real-time output from the development server.
devctl creates a logs folder in your project root:
logs/
βββ dev.log # Development server logs
βββ dev.pid # Process ID file
dev.log: Records all console output from npm run devdev.pid: Stores the current running process IDdevctl start executes npm run dev and runs it in the backgroundlogs/dev.log filelogs/dev.pid fileIf your development server reports that the port is already in use, this is normal. devctl doesn't control port allocation; it only proxies the npm run dev command.
Warning: Process not found, cleaning up PID file
This is normal cleanup behavior. Simply restart:
devctl start
Ensure you have write permissions in the project directory to create the logs folder.
# Clone the project
git clone <repository-url>
cd devctl
# Install dependencies
npm install
# Build project
npm run build
# Link globally (for testing)
npm link
# Run all checks (recommended before committing)
npm run check
# Run individual checks
npm run typecheck # TypeScript type checking
npm run lint # ESLint code checking
npm run test # Run tests
# Code formatting
npm run format # Format all code
npm run format:check # Check formatting status
# Fix ESLint issues
npm run lint:fix
This project uses Husky + lint-staged to ensure code quality. When committing code, it will automatically:
# Add files to staging area
git add .
# Commit (will automatically trigger checks)
git commit -m "feat: add new feature"
This project is licensed under the MIT License.
FAQs
A simple background process manager for npm dev commands
The npm package devctl receives a total of 6 weekly downloads. As such, devctl popularity was classified as not popular.
We found that devctl demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.Β It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
/Research
Socket detected malicious node-ipc versions with obfuscated stealer/backdoor behavior in a developing npm supply chain attack.

Security News
TeamPCP and BreachForums are promoting a Shai-Hulud supply chain attack contest with a $1,000 prize for the biggest package compromise.

Security News
Packagist urges PHP projects to update Composer after a GitHub token format change exposed some GitHub Actions tokens in CI logs.