HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nfl
react-wildcat
JavaScript2015–2020
nfl / react-wildcat

react-wildcat

An opinionated React environment.

3Distinct people
4Mentions
0Explicit recommenders
434GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An opinionated React environment.

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

Observed mentions: 2015-11-04 18:29:44 UTC to 2020-02-23 00:32:07 UTC.

0122015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020

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
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC211
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
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 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101

What Hacker News says

4 sources
Hi there! I used to work at the NFL. We were VERY early adopters of React, and I was lucky enough to work with some of the best frontend engineers I’ve ever worked with in my entire career. We built our own version of NextJs and Create React App 2+ YEARS before those projects became popular in the community (https://github.com/nfl/react-wildcat). This is what I primarily worked on, along with being responsible for making sure NFL.com was accessible, and working on the build/test/deploy pipeline for NFL.com and the NFL.com App (which is react-native). 1.5 years ago my boss and I left and joined System1. Unfortunately, the vast majority of the website was farmed out to contractors, so we weren’t given too much business support to really push some of these open source projects forward and give them the same level of "marketing sparkle" that
Read the rest
a company like Facebook would encourage. For example, part of me was STOKED to see NextJs come out, because it was a better version of react-wildcat. But to be honest part of me felt like with that extra level of marketing sparkle react-wildcat could have been what NextJs was built on to begin with. I don't really fault NFL for this because these projects didn't drive any revenue. Also the way NFL.com's business model worked didn't really give engineering a "wedge" to increase profits, so engineers were all considered a cost center. E.g. at most adtech or publishing companies you can write a few lines of ad related code and prove revenue increased in an A/B test 24 hours later. NFL had no problem selling ads directly because of how amazing their brand is, so fancier code wouldn't really make a difference. Also career-wise I learned even though I got to touch decently high profile open source projects like React Helmet, React GPT, and React Metrics, it didn't really transition to any benefit in job interviews. Before leaving NFL I interviewed at top FANG level companies and got rejected at the phone screen. Even non-FANG companies didn't really seem to care. Keep doing those leetcode problems kids! Most of the original team members from that era of the NFL have moved on to different companies after it became pretty clear that more and more work was going to become outsourced. I got lucky and really clicked with my boss at the NFL, so when he left I tagged along and fumbled (no pun intended) into an absolutely excellent opportunity at System1. All in all, working there was a great experience!
In NFL Has a GitHub Page
Reading this article didn't inspire much hope for a bundle-free JS environment - but if you want to play around with one, we've been working on such an environment that provides 2 applications: 1. A Koa + HTTP2 static asset (primarily JavaScript) server 2. A rendering application that loads a route-based JavaScript dependency tree using JSPM + react-router in order to isomorphically render a web-page. https://github.com/nfl/react-wildcat
In Forgo JavaScript packaging? Not so fast

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.