HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
zloirock
core-js
JavaScript2015–2026
zloirock / core-js

core-js

Standard Library

55Distinct people
59Mentions
0Explicit recommenders
25.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Standard Library

GitHub

Where it is used

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

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:01:32 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 year59 dated mentions

Observed mentions: 2015-03-02 11:36:23 UTC to 2026-08-04 19:02:05 UTC.

0510152015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-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): 16 mentions; 8 submissions, 8 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 11 mentions; 6 submissions, 5 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 15 mentions; 4 submissions, 11 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC413
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
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 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC1688
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC1165
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC211
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC15411
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

16 sources
I see the following when I run npm install on a Create React App. Are these things now verboten as well? Personally It feels a bit yucky to start making package install logs into a kind of bulletin board system so yeah maybe dialing it back a bit is a good idea. Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library! The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: > https://opencollective.com/core-js > https://www.patreon.com/zloirock Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
In NPM Bans Terminal Ads
Yup, just this week I noticed the npm package `core-js` used by the Babel transpiler was polluting my build logs. It listed opencollective and patreon as possible channels of support. That I didn't mind so much, but then there was a message (repeated countless times in the logs) that the author was looking for a job. That's just spam in my terminal, unacceptable. Background and heated discussion in the following GitHub issue (since closed without resolution): Get rid of postinstall message https://github.com/zloirock/core-js/issues/548 I believe some irate users reported it to NPM, which could have triggered or contributed to the policy decision to ban terminal ads.
In NPM Bans Terminal Ads
The problems with this 'funding experiment': - If he does advertising, everyone will eventually start doing it. Then everyone will start using adblockers, defeating the purpose originally planned for. It's a classic case of the Tragedy of the Commons situation [0]. This experiment would have never worked in the long term and only benefits those who do it in the beginning momentarily. - He created a github issue thread asking for feedback from everyone [1], but then closed the issue thread. Later one he went on saying that he doesn't care what people say unless they're contributors to the library [2]. He could have just limited the thread to contributors only but he prefers pushing the goal post. - If you can no longer support OSS, then hand it over to an organization open to the community, or archive the project. As an example, Fatih arch
Read the rest
ived projects he could no longer support and the community had no issues at all [3]. People who can contribute will fork the project and continue with it. - The core-js maintainer started doing ads like that first, promoting his own job advertisement [4]. It got to the point where he started deleting comments and blocking people on github which he disagreed with. Keep in mind that this is a package with million of weekly installs and used by babel libraries so people's output logs looked like this [5]. I believe it was violating NPM's terms of service too. - Authors can do whatever they want with their own packages including spamming post install logs with ads, but expect the programming community to be very vocal against the practice [6]. A package meant for the community should listen to the feedback of the community, instead of calling them wrong. [0] https://en.wikipedia.org/wiki/Tragedy_of_the_commons [1] https://github.com/standard/standard/issues/1381 [2] https://twitter.com/feross/status/1165515455882096640?s=20 [3] https://arslan.io/2018/10/09/taking-an-indefinite-sabbatical... [4] https://github.com/zloirock/core-js/issues/548 [5] https://github.com/zloirock/core-js/issues/548#issuecomment-... [6] https://www.reddit.com/r/programming/comments/cus0zu/a_3mil_...
In Recap of the `funding` experiment
Thanks for the link, I was indeed unaware of the term. By looking through the ongoing discussion, it was interesting to find a reference to the core-js issue [0] from earlier this year. Its maintainer, with his established position in the npm community, makes use of a similar post-install script to open up a discussion and communicate his situation. This gives him a more direct communication channel to its users without directly helping his situation. What I assume can be understood as a rent-seeking practice, is how fooreys intention, with the same political power in maintaining a popular package, seems not to be solely to raise awareness to his situation. But instead he's forced a solution to his problem by advertising unrelated 3rd party products. Whereas he interestingly also uses the term experiment, it did already render npm as a sp
Read the rest
In Standard JS: npm install funding

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

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.