StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Application Performance Monitoring
  4. Node Js Process Manager
  5. forever vs nodemon

forever vs nodemon

OverviewComparisonAlternatives

Overview

forever
forever
Stacks148
Followers125
Votes0
nodemon
nodemon
Stacks3.3K
Followers195
Votes2
GitHub Stars26.7K
Forks1.7K

forever vs nodemon: What are the differences?

Introduction

In this article, we will discuss the key differences between forever and nodemon, two popular utility tools used in Node.js development. Both forever and nodemon aim to improve the development workflow by automatically restarting the server when file changes are detected. However, there are some key differences between the two that we will explore below.

  1. Installation: One key difference between forever and nodemon is the process of installation. Forever is a global npm module that needs to be installed globally on your system using the command npm install -g forever. On the other hand, nodemon can be installed locally within your project's directory using the command npm install nodemon.

  2. Configuration: Forever has a simpler configuration process compared to nodemon. It requires only a single command to start a server using the syntax forever start app.js. In contrast, nodemon provides more advanced configuration options through a nodemon.json file or the command line arguments.

  3. File Monitoring: Another significant difference between the two is the way they monitor files for changes. Forever has a basic file monitoring feature that requires a manual restart if any file is modified. In contrast, nodemon excels in this aspect by automatically restarting the server whenever a file change is detected, making it more convenient for developers.

  4. Logging: Forever provides comprehensive logging information about each script it runs. It displays the beginning and end times, console output, exit status, and more. Nodemon, although it also logs certain events, does not provide as detailed information as forever.

  5. Platform Support: Forever is a cross-platform utility tool, meaning it can be used on various operating systems, including Windows, macOS, and Linux. Nodemon, on the other hand, is primarily designed for Unix-based systems, making it less compatible with Windows.

  6. Community and Maintenance: Forever has been around for a longer time and has a larger community of users and contributors. It is actively maintained and regularly receives updates and bug fixes. While nodemon also has a considerable user base, it may not receive updates and new features as frequently as forever.

In summary, forever and nodemon differ in terms of installation process, configuration, file monitoring capabilities, logging functionality, platform support, and community/maintenance. Understanding these differences can help developers choose the most suitable tool for their specific needs.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

forever
forever
nodemon
nodemon

It is a simple CLI tool for ensuring that a given script runs continuously. It is used to keep the server alive even when the server crash/stops. When the server is stopped because of some error, exception, etc.it automatically restarts it.

It is an open source utility that will monitor for any changes in your source and automatically restart your server. It has a default support for node & coffeescript, but easy to run any executable (such as python, make, etc).

Command Line Utility; keep the server alive; ensuring that a given script runs continuously
Automatic restarting of application; Detects default file extension to monitor
Statistics
GitHub Stars
-
GitHub Stars
26.7K
GitHub Forks
-
GitHub Forks
1.7K
Stacks
148
Stacks
3.3K
Followers
125
Followers
195
Votes
0
Votes
2
Pros & Cons
No community feedback yet
Pros
  • 1
    Easy to use
  • 1
    It's lightweight
Integrations
Node.js
Node.js
ExpressJS
ExpressJS
TypeScript
TypeScript
Node.js
Node.js

What are some alternatives to forever, nodemon?

PM2

PM2

Production process manager for Node.js apps with a built-in load balancer

Nodetime

Nodetime

Nodetime is an application performance management toolset in the cloud - an all-round solution for performance monitoring, optimization and troubleshooting.

Supervisord

Supervisord

It allows its users to monitor and control a number of processes on UNIX-like operating systems. It shares some of the same goals of programs like launchd, daemontools, and runit. it is meant to be used to control processes related to a project or a customer, and is meant to start like any other program at boot time.

nodejs-dashboard

nodejs-dashboard

Determine in realtime what's happening inside your node process from the terminal. No need to instrument code to get the deets. Also splits stderr/stdout to help spot errors sooner.

NodeFly

NodeFly

NodeFly APM provides real-time monitoring for your Node.js application. Simplicity is the key! We allow our users to gain detailed, real-time performance monitoring of your Node.js application services so they can see everything that is happening, as it happens. This includes understanding system usage at every moment in time to uncover and resolve issues within the application as they arise.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana