HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mikeal
r2
JavaScript2017–2017
mikeal / r2

r2

HTTP client. Spiritual successor to request.

Web DevelopmentNetworking
Explore on GitHubRead Hacker News discussions
4Distinct people
4Mentions
0Explicit recommenders
4.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

HTTP client. Spiritual successor to request.

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

Observed mentions: 2017-08-31 15:58:04 UTC to 2017-09-22 12:38:02 UTC.

0122017-08-31 00:00:00 UTC to 2017-09-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 312017-09-01 00:00:00 UTC to 2017-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-02 00:00:00 UTC to 2017-09-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-03 00:00:00 UTC to 2017-09-04 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2017-09-04 00:00:00 UTC to 2017-09-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-05 00:00:00 UTC to 2017-09-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-06 00:00:00 UTC to 2017-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-07 00:00:00 UTC to 2017-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-08 00:00:00 UTC to 2017-09-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-09 00:00:00 UTC to 2017-09-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-10 00:00:00 UTC to 2017-09-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-11 00:00:00 UTC to 2017-09-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 112017-09-12 00:00:00 UTC to 2017-09-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-13 00:00:00 UTC to 2017-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-14 00:00:00 UTC to 2017-09-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-15 00:00:00 UTC to 2017-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-16 00:00:00 UTC to 2017-09-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-17 00:00:00 UTC to 2017-09-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-18 00:00:00 UTC to 2017-09-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-19 00:00:00 UTC to 2017-09-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-20 00:00:00 UTC to 2017-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-21 00:00:00 UTC to 2017-09-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-22 00:00:00 UTC to 2017-09-23 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 22

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 312017-08-31 00:00:00 UTC2017-09-01 00:00:00 UTC110
Sep 12017-09-01 00:00:00 UTC2017-09-02 00:00:00 UTC000
Sep 22017-09-02 00:00:00 UTC2017-09-03 00:00:00 UTC000
Sep 32017-09-03 00:00:00 UTC2017-09-04 00:00:00 UTC220
Sep 42017-09-04 00:00:00 UTC2017-09-05 00:00:00 UTC000
Sep 52017-09-05 00:00:00 UTC2017-09-06 00:00:00 UTC000
Sep 62017-09-06 00:00:00 UTC2017-09-07 00:00:00 UTC000
Sep 72017-09-07 00:00:00 UTC2017-09-08 00:00:00 UTC000
Sep 82017-09-08 00:00:00 UTC2017-09-09 00:00:00 UTC000
Sep 92017-09-09 00:00:00 UTC2017-09-10 00:00:00 UTC000
Sep 102017-09-10 00:00:00 UTC2017-09-11 00:00:00 UTC000
Sep 112017-09-11 00:00:00 UTC2017-09-12 00:00:00 UTC000
Sep 122017-09-12 00:00:00 UTC2017-09-13 00:00:00 UTC000
Sep 132017-09-13 00:00:00 UTC2017-09-14 00:00:00 UTC000
Sep 142017-09-14 00:00:00 UTC2017-09-15 00:00:00 UTC000
Sep 152017-09-15 00:00:00 UTC2017-09-16 00:00:00 UTC000
Sep 162017-09-16 00:00:00 UTC2017-09-17 00:00:00 UTC000
Sep 172017-09-17 00:00:00 UTC2017-09-18 00:00:00 UTC000
Sep 182017-09-18 00:00:00 UTC2017-09-19 00:00:00 UTC000
Sep 192017-09-19 00:00:00 UTC2017-09-20 00:00:00 UTC000
Sep 202017-09-20 00:00:00 UTC2017-09-21 00:00:00 UTC000
Sep 212017-09-21 00:00:00 UTC2017-09-22 00:00:00 UTC000
Sep 222017-09-22 00:00:00 UTC2017-09-23 00:00:00 UTC101

What Hacker News says

4 sources
styfle·Sep 22, 2017
I read about @std/esm and I wasn't totally sold on it. But now that I read the browser side of the story, I think it makes way more sense to make use of @std/esm in all packages on npm. The old way of doing things was write for node, and transpile/polyfill the browser with browserify/webpack/etc. But the amount of bytes you ship to the browser really matters. So now the new way of doing things is to write for the browser and transpile/polyfill node which is what @std/esm is doing. This is explained a little better in the r2 readme: https://github.com/mikeal/r2
In Deploying ES2015+ Code in Production Today

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.