HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
expressjs
express
JavaScript2009–2026
expressjs / express

express

Fast, unopinionated, minimalist web framework for node.

72Distinct people
79Mentions
3Explicit recommenders
69.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fast, unopinionated, minimalist web framework for node.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I highly recommend reading "The Do's and Don'ts of Client Authentication on the Web" [1] from MIT. It's rather old and not very well-known, but it's excellent. The concepts…

drderidder used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.

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

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

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

Mentions over time

HN mentions by year79 dated mentions

Observed mentions: 2009-11-19 21:46:03 UTC to 2026-02-03 03:42:37 UTC.

0510152009-01-01 00:00:00 UTC to 2010-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20092010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 17 mentions; 8 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 6 submissions, 7 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20092009-01-01 00:00:00 UTC2010-01-01 00:00:00 UTC110
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC505
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC606
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC303
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC13211
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC312
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1789
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC211
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC303
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC1367
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

What Hacker News says

6 sources
Express is very flexible, and can work in just about any way you could imagine. Take no offense but it sounds like you aren't very familiar with javascript or node.js and that is okay, but there is much to learn about project organization. It is actually quite easy to organize your code similar to a rails mvc application, the key is being consistent. If you want to see a working example of an mvc style express application, then look at the examples provided with express: https://github.com/visionmedia/express/tree/master/examples/... Again, there are many ways to organize your applications, just look around at what other people have done, or use the examples, and you should be able to make yours handle just the same.
In Node.js modules you should know about: socket.io
No. Keeping all your code in one file is a recipe for maintainability disaster. I've found that with Javascript, proper project organization is even more important than with some other languages. It sounds like you haven't become familiar with Node's CommonJS compatible module system. Try starting there: http://nodejs.org/docs/latest/api/modules.html Once you understand the basics of modules and requiring, I'd take a look at the ExpressJS example apps for organization ideas: https://github.com/visionmedia/express/tree/master/examples
In Node.js modules you should know about: socket.io
Here's a list of CRUD+ apps that I keep open in textmate to consult as examples: I suck at formatting here; apologies in advance. Alex Young's NodePad (from daily.js) (more than a simple CRUD app but helpful nonetheless) https://github.com/alexyoung/nodepad Individual Node + Express examples by TJ (as mentioned in another post) https://github.com/visionmedia/express/tree/master/examples Another basic Node+Express example (by TJ again) https://github.com/visionmedia/finance Guillermo posted a CRUD with Express + Mongoose a few days ago https://github.com/guille/mongoose-meetup-04-05/ There's another VERY simple CRUD app somewhere in the Mongoose Google group as a zipfile(yes, this uses Mongoose as well obviously). I can't seem to find it right now, but I think Siegfried Ehret was the original poster. Email me if you'd lik
Read the rest
e me to send it to you. Also try nodetuts.com. Pedro's stuff helped me when I started learning a few months ago. Some of his stuff might be out-of-date but it will still help you conceptually (and not all of it is by any means). Some out-of-dateness will just be making simple code changes (like upgrading Express). Hope this helps!
In The Node Beginner Book
I definitely noticed this weird lack of information on Express. I've found the best thing is to check out the examples from Express' own github: https://github.com/visionmedia/express/tree/master/examples That's useful to see how something is done, but not why or the different options available. For that, there's still a definite lack of a clear guide. The guide on the Express website reads more like an API reference and doesn't go into detail on how to use the different features, which I think would be very helpful. Right now I'm working on my first application using Express. Over the Summer, when I have free time, I'd like to write a tutorial series for Express and put it up on github so it can be updated as Express evolves. That's really one of the main issues right now, all this stuff is changing so rapidly that a tutorial can become
Read the rest
outdated in a few months.
In The Node Beginner Book
This are a few of the things that I am to following : Server side: Testing: - Expresso [1]: TDD framework for node -- high speed parallel testing! - Zombie.js [2]: fast, headless full-stack testing using Node.js Tools: - load.js [3]: Lazy load your JS - npm [4] a package manager for node - JSDoc [5] Documentation tool - Docco [6] Literate documentation. - underscore [7] provides a lot of the functional programming - node-openid [8] openid. Frameworks: - Express [8] Sinatra inspired web development framework for node [1] http://visionmedia.github.com/expresso/ [2] http://zombie.labnotes.org/ [3] https://github.com/chriso/load.js [4] https://github.com/isaacs/npm [5] https://github.com/micmath/JSDoc [6] https://github.com/jashkenas/docco [7] http://documentcloud.github.com/underscore/ [8] https://github.com/havard/node-openid [9] https://g
Read the rest
In Ask HN: The State of the Javascript Ecosystem?

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.