HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pilagod
js-tracker
TypeScript2018–2018
pilagod / js-tracker · Archived

js-tracker

A chrome extension tracks front-end JavaScript that uses DOM / jQuery APIs to manipulate html dom elements (e.g., change style, attach event listener) at runtime.

2Distinct people
2Mentions
0Explicit recommenders
399GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A chrome extension tracks front-end JavaScript that uses DOM / jQuery APIs to manipulate html dom elements (e.g., change style, attach event listener) at runtime.

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:03:16 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 hour2 dated mentions

Observed mentions: 2018-02-27 14:10:28 UTC to 2018-02-27 20:55:02 UTC.

012018-02-27 14:00:00 UTC to 2018-02-27 15:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 27, 14:002018-02-27 15:00:00 UTC to 2018-02-27 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-27 16:00:00 UTC to 2018-02-27 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-27 17:00:00 UTC to 2018-02-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 27, 17:002018-02-27 18:00:00 UTC to 2018-02-27 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-27 19:00:00 UTC to 2018-02-27 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-27 20:00:00 UTC to 2018-02-27 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 27, 20:00

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
Feb 27, 14:002018-02-27 14:00:00 UTC2018-02-27 15:00:00 UTC110
Feb 27, 15:002018-02-27 15:00:00 UTC2018-02-27 16:00:00 UTC000
Feb 27, 16:002018-02-27 16:00:00 UTC2018-02-27 17:00:00 UTC000
Feb 27, 17:002018-02-27 17:00:00 UTC2018-02-27 18:00:00 UTC000
Feb 27, 18:002018-02-27 18:00:00 UTC2018-02-27 19:00:00 UTC000
Feb 27, 19:002018-02-27 19:00:00 UTC2018-02-27 20:00:00 UTC000
Feb 27, 20:002018-02-27 20:00:00 UTC2018-02-27 21:00:00 UTC101

What Hacker News says

2 sources
Not entirely right, though I do love the Perf tab. (Disclosure: I work on it.) This extension adds instrumentation to listen to changes to DOM nodes and style attributes. And it reports exactly what the change was: https://github.com/pilagod/js-tracker/blob/master/src/tracke... That level of detail isn't really provided in the Perf tab, as it's quite invasive and can have significant perf overhead in a busy webapp. (DevTools does have a hidden experiment called "Timeline: Invalidation Tracking" which does report on various DOM/CSS changes, though. It's cool). Also, I should point out a _very_ similar extension my mate built: https://github.com/kdzwinel/DOMListenerExtension Same basic idea, but just reporting every change to DOM nodes that a MutationObserver can see.
In Show HN: A Chrome extension that tracks front-end JavaScript at runtime

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.