HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cesarandreu
web-app
JavaScript2015–2016
cesarandreu / web-app

web-app

Reasonable starting point for building a web app

2Distinct people
10Mentions
0Explicit recommenders
303GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Reasonable starting point for building a web app

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, 1:49:46 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 week10 dated mentions

Observed mentions: 2015-06-21 02:47:59 UTC to 2016-01-20 10:56:57 UTC. Weeks start Monday, UTC.

01232015-06-15 00:00:00 UTC to 2015-06-22 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsJun 152015-06-22 00:00:00 UTC to 2015-06-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-29 00:00:00 UTC to 2015-07-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-06 00:00:00 UTC to 2015-07-13 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-07-13 00:00:00 UTC to 2015-07-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-07-20 00:00:00 UTC to 2015-07-27 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2015-07-27 00:00:00 UTC to 2015-08-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-03 00:00:00 UTC to 2015-08-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-10 00:00:00 UTC to 2015-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-17 00:00:00 UTC to 2015-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-24 00:00:00 UTC to 2015-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-31 00:00:00 UTC to 2015-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-07 00:00:00 UTC to 2015-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-14 00:00:00 UTC to 2015-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-21 00:00:00 UTC to 2015-09-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-28 00:00:00 UTC to 2015-10-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 282015-10-05 00:00:00 UTC to 2015-10-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-12 00:00:00 UTC to 2015-10-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-19 00:00:00 UTC to 2015-10-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-26 00:00:00 UTC to 2015-11-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-02 00:00:00 UTC to 2015-11-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-09 00:00:00 UTC to 2015-11-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-16 00:00:00 UTC to 2015-11-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-23 00:00:00 UTC to 2015-11-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-30 00:00:00 UTC to 2015-12-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-07 00:00:00 UTC to 2015-12-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-14 00:00:00 UTC to 2015-12-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-21 00:00:00 UTC to 2015-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-28 00:00:00 UTC to 2016-01-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-04 00:00:00 UTC to 2016-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-11 00:00:00 UTC to 2016-01-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-18 00:00:00 UTC to 2016-01-25 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJan 18

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
Jun 152015-06-15 00:00:00 UTC2015-06-22 00:00:00 UTC303
Jun 222015-06-22 00:00:00 UTC2015-06-29 00:00:00 UTC000
Jun 292015-06-29 00:00:00 UTC2015-07-06 00:00:00 UTC000
Jul 62015-07-06 00:00:00 UTC2015-07-13 00:00:00 UTC202
Jul 132015-07-13 00:00:00 UTC2015-07-20 00:00:00 UTC000
Jul 202015-07-20 00:00:00 UTC2015-07-27 00:00:00 UTC303
Jul 272015-07-27 00:00:00 UTC2015-08-03 00:00:00 UTC000
Aug 32015-08-03 00:00:00 UTC2015-08-10 00:00:00 UTC000
Aug 102015-08-10 00:00:00 UTC2015-08-17 00:00:00 UTC000
Aug 172015-08-17 00:00:00 UTC2015-08-24 00:00:00 UTC000
Aug 242015-08-24 00:00:00 UTC2015-08-31 00:00:00 UTC000
Aug 312015-08-31 00:00:00 UTC2015-09-07 00:00:00 UTC000
Sep 72015-09-07 00:00:00 UTC2015-09-14 00:00:00 UTC000
Sep 142015-09-14 00:00:00 UTC2015-09-21 00:00:00 UTC000
Sep 212015-09-21 00:00:00 UTC2015-09-28 00:00:00 UTC000
Sep 282015-09-28 00:00:00 UTC2015-10-05 00:00:00 UTC000
Oct 52015-10-05 00:00:00 UTC2015-10-12 00:00:00 UTC000
Oct 122015-10-12 00:00:00 UTC2015-10-19 00:00:00 UTC000
Oct 192015-10-19 00:00:00 UTC2015-10-26 00:00:00 UTC000
Oct 262015-10-26 00:00:00 UTC2015-11-02 00:00:00 UTC000
Nov 22015-11-02 00:00:00 UTC2015-11-09 00:00:00 UTC000
Nov 92015-11-09 00:00:00 UTC2015-11-16 00:00:00 UTC000
Nov 162015-11-16 00:00:00 UTC2015-11-23 00:00:00 UTC000
Nov 232015-11-23 00:00:00 UTC2015-11-30 00:00:00 UTC000
Nov 302015-11-30 00:00:00 UTC2015-12-07 00:00:00 UTC000
Dec 72015-12-07 00:00:00 UTC2015-12-14 00:00:00 UTC000
Dec 142015-12-14 00:00:00 UTC2015-12-21 00:00:00 UTC000
Dec 212015-12-21 00:00:00 UTC2015-12-28 00:00:00 UTC000
Dec 282015-12-28 00:00:00 UTC2016-01-04 00:00:00 UTC000
Jan 42016-01-04 00:00:00 UTC2016-01-11 00:00:00 UTC000
Jan 112016-01-11 00:00:00 UTC2016-01-18 00:00:00 UTC000
Jan 182016-01-18 00:00:00 UTC2016-01-25 00:00:00 UTC202

What Hacker News says

10 sources
If you want to check out an alternative for building applications, go look up Webpack. I strongly believe you can build web applications without having to pull in Gulp or Grunt. And to back up my claim I setup a project [0] that shows how to do it using webpack + npm run-scripts. I'd argue it solves a large set of problems while maintaining a reasonable level of complexity. [0] https://github.com/cesarandreu/web-app
In Create a character voting app using React, Node.js, MongoDB and Socket.io
I made a scaffold [0] that tries to give you a reasonable starting point, without tons of extra cruft. It was important to me that the scaffold handle all 3 basic environments: development, testing, and production. It's basically a single webpack config (that's heavily commented, btw!) and a set of npm run-scripts. You don't need gulp to build an application! And I would not call bower a sane way to include frontend dependencies... Not by a long shot. [0] https://github.com/cesarandreu/web-app
In Create a character voting app using React, Node.js, MongoDB and Socket.io
I challenge your assumption that gulp + browserify is more straightforward than webpack. Your setup is not representative of a real application. I setup a project scaffold [0] with a configuration that supports development, production, and testing environments. It has a heavily commented webpack config. No tests? No asset cache busting by updating name references? Come on, those are basic requirements for a web project. On top of that, webpack lets your dependencies be resolved as part of your code, instead of relying on certain files being in certain folders: e.g. your css and images. [0] http://github.com/cesarandreu/web-app
In Create a character voting app using React, Node.js, MongoDB and Socket.io
I setup a repo [0] with a boilerplate that actually covers all the bases for a real web app, because I realized just how annoying and difficult it could be to get something setup. [1] It provides an environment for development, testing, and production environments. In development, hotloading / live reload of assets when possible, and refresh otherwise. In production it'll do proper cache busting and asset minification. While testing it generates code coverage! Best part? No gulp or grunt. It's all basically a heavily commented webpack config and a few npm scripts. All of the people that have responded to you so far seem to disregard at least one of the details that I consider important. Mainly, it should have all the tasks needed for a web app that you plan on working on for a period longer than a few days, and it shouldn't make you deal
Read the rest
with more build tool bullshit than is necessary. I don't have any examples of big projects using web-app without modifications, however, I have a small example: quad-blog [2], which is my blog. It's written with fluxible, and the webpack config for that project is based on web-app. It takes it a step further and does isomorphic (or universal) javascript, so it'll do server-side rendering and then delegate to the client once it's loaded. One other highlight of the project is that it uses Koa, so you get real middleware (as in, middleware that behaves like a stack). Oh, and it uses Sequelize and shows how you'd do database migrations with an awesome relational database: Postgres, instead of taking the NoSQL shortcut (which is woefully inadequate for a lot of applications). [0] http://github.com/cesarandreu/web-app [1] https://blog.cesarandreu.com/posts/a_reasonable_starting_poi... [2] https://github.com/cesarandreu/quad-blog/
In React on ES6+
I use it at work and for personal projects. It's great, creating sophisticated interactions is a lot simpler with flux and react. Flux is very boilerplate-y, even with some of the lighter frameworks. But boilerplate isn't particularly complicated, so you get over it. If I were going to a hackathon I would not use flux+react, I'd probably go with angular. If it's something I plan on maintaining over a long period of time, react is currently my big choice. Testing react is very nice, especially coming from angular where testing directives was very painful. (And testing everything else was needlessly verbose.) I made a VERY simple project starter [0] that I'm going to take the chance to plug now. It's built for frontend web applications in mind, and it focuses on giving you the starting environment to build an app. It provides development, t
Read the rest
esting, and production builds. In development you get live-reload and hot-loading of assets. In production you get minification, concatenation, and cache busting of assets, as well as getting all assets copied to your output folder. There's a live testing environment (i.e. watch files and run tests) as well as a single-run environment. Tests also generate code coverage reports. The best part is that it doesn't use gulp or grunt, it's just a webpack config with a few flags per environment type, and to run every task you just use npm run-scripts. Out of the box it handles ES6/ES7/JSX, CSS, images and fonts, but extending it to support other assets is trivial. I took the time to heavily comment the webpack config in order to help people out. EDIT: My coworker pestered me to edit this and mention that we're hiring [1]. If you're interested in using React and Flux, reach out! [0] https://github.com/cesarandreu/web-app [1] http://www.treasuredata.com/careers
In Ask HN: ReactJS – Do you use it? Do you like it?

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.