HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
remy
nodemon
JavaScript2013–2018
remy / nodemon

nodemon

Monitor for any changes in your node.js application and automatically restart the server - perfect for development

9Distinct people
9Mentions
0Explicit recommenders
26.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Monitor for any changes in your node.js application and automatically restart the server - perfect for development

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year9 dated mentions

Observed mentions: 2013-05-30 22:40:14 UTC to 2018-11-27 17:16:09 UTC.

01232013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2018

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC303
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC000
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC211
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303

What Hacker News says

9 sources
I'm not familiar with the Node ecosystem but people blaming the maintainer for giving control of one of his unmaintained repos to a third party is frankly ludicrous to me. I mean, why did you even trust the original maintainer in the first place? How do you know that if somebody had decided to pay him a million dollar to backdoor his package, he wouldn't have done it? Did you pay a private eye to conduct a private investigation on them? If the other dev who injected the backdoor had waited a year or so, pretending to actually maintain the package first, what then? If you're writing code dealing with sensitive information (say, credit card, cryptocurrency credentials, private information etc...) and you don't even bother to vet your dependencies and when it blows in your face your first reflex is to shift blame on some guy who's giving you
Read the rest
r source code free on the internet you should really think hard about what you're doing. Can you imagine that flying in any other industry? "Bridge collapses because company bought crappy steel from some guy off e-bay, but hey he had a trustworthy nickname." I mean, the injection was finally discovered because of a deprecation warning: https://github.com/remy/nodemon/issues/1442 I wonder how many backdoored node packages there are out there, but judging by how this issue was handled I'd guess probably more than 0. If there's one positive consequence to this cryptocurrency craze it's that it shines light on our terrible so-called "engineering" practices in the software industry.
In Statement on NPM Package Vulnerability in v5.0.2-5.1.0 of Copay Bitcoin Wallets
I've seen nodemon before and this is what worried me the most: "nodemon has three potential methods it uses to look for file changes. First, it polls using the find command to search for files modified within the last second. This method works on systems with a BSD based find (Mac, for example)." Especially on Mac OSX why would you prefer to use an external command like find instead of using Kqueue? I wonder if find is the right tool for that. And I wonder again why only on BSD-based systems when linux also has find. Gotta read a bit more about that. fyi, this is how nodemon is doing file checking: find -L /dev/null -type f -mtime -1s -print (https://github.com/remy/nodemon/blob/master/nodemon.js#L57)
In Show HN: My nodejs-supervisor like tool, written in Go
I was just looking into inotify to reload nginx and various other services on conf changes. I guess I'll go with Watchman so I don't have to write a series of shell scripts. I considered guard (https://github.com/guard/guard) and Nodemon (https://github.com/remy/nodemon), but Watchman has less dependencies (doesn't require Ruby/Node). There's also Supervisor (Python) (http://supervisord.org/), but I think that is more process management. I'm not sure if it can do file-watching as simply as Watchman.
In Watchman: Faster builds with large source trees

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.