November 17, 2025 at 7:53:16 PM UTC

Nexodus Archive

A versioned archive of posts from Bluesky, Mastodon, GitHub, npm, YouTube, Letterboxd, Hacker News, and blogs. Browse the most popular posts.

Last built Nov 7, 2026, 1:18 PM UTC.

	Since	posts	replies	likes	reposts and quotes	views
Bluesky	May 2023	1,039	8,236	23,127	2,380
Mastodon	Nov 2022	2,399	29,156	55,396	16,820
GitHub	Jul 2010	179	5,777 3,520	33,866	3,317
npm	Jul 2014	139	1,546			75,991,720
YouTube	Dec 2015	30		1,203		32,713
Letterboxd	Mar 2026	55
Blog	Nov 2025	20
Hacker News	Jan 2011	59	575	802
All	Jul 2010	4,807	37,967	114,394	22,517	76,024,433

8 2010
4 2011
3 2012
6 2013
9 2014
55 2015
78 2016
110 2017
101 2018
66 2019
134 2020
201 2021
327 2022
998 2023
879 2024
1,035 2025
793 2026

4,807 posts by year

“are the devtools keeping pace with emerging web standards?” is a very good litmus test for whether a browser vendor is investing alongside the web or just treading water

4 replies

Alex Grant 3 days later

@zachleat
Afaik, chrome hasn't implemented code coverage for service workers yet.
Just saying
1. Alex Russell 3 days later
  
  @localnerve @zachleat is there a crbug for it? I can route
  1. Alex Grant 3 days later
    
    @slightlyoff @zachleat
    I searched https://issues.chromium.org/ but couldn't find one.
    Back this summer when I was developing my pwa reference, I found a github issue from 2018 (can't relocate rn) that suggests istanbul instrumentation is the only way. That's what I ended up employing in my jam-build pwa reference - works. But gosh its crazy things haven't progressed in ~10 years...
    1. Alex Russell 3 days later
      
      @localnerve @zachleat It will not have escaped your notice that browsers are complex, but we are extremely grateful for bug reports. It's not "crazy" that something was missed, but we appreciate reports.