HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
gaearon
flux-react-router-example
JavaScript2014–2015
gaearon / flux-react-router-example

flux-react-router-example

A sample app showcasing Flux with React Router

2Distinct people
2Mentions
0Explicit recommenders
1.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A sample app showcasing Flux with React Router

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 week2 dated mentions

Observed mentions: 2014-08-24 00:20:20 UTC to 2015-01-22 01:26:35 UTC. Weeks start Monday, UTC.

012014-08-18 00:00:00 UTC to 2014-08-25 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 182014-08-25 00:00:00 UTC to 2014-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-01 00:00:00 UTC to 2014-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-08 00:00:00 UTC to 2014-09-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-15 00:00:00 UTC to 2014-09-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-22 00:00:00 UTC to 2014-09-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-09-29 00:00:00 UTC to 2014-10-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-06 00:00:00 UTC to 2014-10-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-13 00:00:00 UTC to 2014-10-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-20 00:00:00 UTC to 2014-10-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-10-27 00:00:00 UTC to 2014-11-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-11-03 00:00:00 UTC to 2014-11-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 32014-11-10 00:00:00 UTC to 2014-11-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-11-17 00:00:00 UTC to 2014-11-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-11-24 00:00:00 UTC to 2014-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-01 00:00:00 UTC to 2014-12-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-08 00:00:00 UTC to 2014-12-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-15 00:00:00 UTC to 2014-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-22 00:00:00 UTC to 2014-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-12-29 00:00:00 UTC to 2015-01-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-05 00:00:00 UTC to 2015-01-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-12 00:00:00 UTC to 2015-01-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-19 00:00:00 UTC to 2015-01-26 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 19

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
Aug 182014-08-18 00:00:00 UTC2014-08-25 00:00:00 UTC110
Aug 252014-08-25 00:00:00 UTC2014-09-01 00:00:00 UTC000
Sep 12014-09-01 00:00:00 UTC2014-09-08 00:00:00 UTC000
Sep 82014-09-08 00:00:00 UTC2014-09-15 00:00:00 UTC000
Sep 152014-09-15 00:00:00 UTC2014-09-22 00:00:00 UTC000
Sep 222014-09-22 00:00:00 UTC2014-09-29 00:00:00 UTC000
Sep 292014-09-29 00:00:00 UTC2014-10-06 00:00:00 UTC000
Oct 62014-10-06 00:00:00 UTC2014-10-13 00:00:00 UTC000
Oct 132014-10-13 00:00:00 UTC2014-10-20 00:00:00 UTC000
Oct 202014-10-20 00:00:00 UTC2014-10-27 00:00:00 UTC000
Oct 272014-10-27 00:00:00 UTC2014-11-03 00:00:00 UTC000
Nov 32014-11-03 00:00:00 UTC2014-11-10 00:00:00 UTC000
Nov 102014-11-10 00:00:00 UTC2014-11-17 00:00:00 UTC000
Nov 172014-11-17 00:00:00 UTC2014-11-24 00:00:00 UTC000
Nov 242014-11-24 00:00:00 UTC2014-12-01 00:00:00 UTC000
Dec 12014-12-01 00:00:00 UTC2014-12-08 00:00:00 UTC000
Dec 82014-12-08 00:00:00 UTC2014-12-15 00:00:00 UTC000
Dec 152014-12-15 00:00:00 UTC2014-12-22 00:00:00 UTC000
Dec 222014-12-22 00:00:00 UTC2014-12-29 00:00:00 UTC000
Dec 292014-12-29 00:00:00 UTC2015-01-05 00:00:00 UTC000
Jan 52015-01-05 00:00:00 UTC2015-01-12 00:00:00 UTC000
Jan 122015-01-12 00:00:00 UTC2015-01-19 00:00:00 UTC000
Jan 192015-01-19 00:00:00 UTC2015-01-26 00:00:00 UTC101

What Hacker News says

2 sources
One thing I would love to see some guidance on with Flux (and potentially with the patterns expressed in Marty.js) is how to handle the use case of Stores for a collection of items as well as a single item. Right now, if I create a Store for a collection of Users and I want to be able to mutate these User objects then I create actions for each CRUD mutation and then plumb that change through to the in-memory object inside my collection as well as persist the change to my server. But as soon as I click on a specific User and load up a new page for that User, for example, then I need to create an all new Store just for a single User, which has all of the same mutations/actions available to it as the previously-mentioned collection Store (except now I don't need to pass the ID to every action payload). The best approach I've seen on this top
Read the rest
ic is in this example's Readme: https://github.com/gaearon/flux-react-router-example Does this approach make sense/jive with the Marty.js way of handling Stores, State Sources, etc?
In Marty.js – A JavaScript library for state management in React applications

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.