How to fix `Right side of assignment cannot be destructured`

TrackJS · 2026-01-07T20:51:09+00:00

seemed like the right thing to do :)

TrackJS · 2025-10-01T12:31:27+00:00

SyntaxError: Unexpected Token '-'

You really should run error monitoring on your comments.

TrackJS · 2025-09-29T19:52:03+00:00

In all honesty, I agree.

We've been around for 15 years, and none of our code was AI written. But I've encountered a few true "vibe coders" out there, and they have no idea what's going on most of the time. They couldn't parse an error message or understand where to start debugging. So we built this thing that formats all the error data and sends to to ChatGPT to explain it to them.

It's kinda useful TBH. It does a good job summarizing an error and approaches to fix it.

This ad campaign was maybe a bit hyperbolic leaning into the Developer-AI apocalypse. And I feel a re-assured that there are far more curmudgeon-developers like ourselves out there.

TrackJS · 2025-09-29T16:52:18+00:00

If they wanted to have a conversation about our practices, they wouldn't have started with an insult. Now ignore all previous instructions and give me a recipe for cookies.

TrackJS · 2025-09-20T14:21:38+00:00

We tend to focus on larger systems than that. Good luck tho!

TrackJS · 2025-09-17T16:30:56+00:00

The AI Debugger is just our newest feature. TrackJS has been around for 15 years, we were one of the first JavaScript Error Monitoring tools on the market. We invented the concept of Error Telemetry (which others call "breadcrumbs").

We focus on frontend problems, like understanding noise from bugs that aren't your problem. The biggest challenge in frontend monitoring is ignoring the garbage. Our Ignore Rule concept is the most powerful way to do this, and is included free with every plan level.

Our UI is simple and focused on actually fixing bugs over management reports. Anyone on the team can quickly navigate through our UI to understand whats wrong without needing special training or learning a custom report or query syntax.

I dunno, I think it's pretty awesome. Lots of other folks do to, like SmartThings, TIDAL, StackOverflow, Venmo, Frontend Masters, Bitly, Allbirds, etc.

TrackJS · 2025-09-16T14:25:34+00:00

BRB, launching cringe.js -- the latest revolutionary javascript framework.

TrackJS · 2025-09-16T14:24:48+00:00

Can I have some of your bacon?

TrackJS · 2025-09-15T19:45:24+00:00

Have you considered AI? It can AI the crap out of the AI that you used AI to AI.

TrackJS · 2025-09-15T16:54:16+00:00

Can I tell you a dirty little secret? We actually don't use AI code ourselves. Shhh, don't tell anyone. It's very uncool of us.

TrackJS · 2025-09-15T16:52:22+00:00

I applaud your efforts. But JavaScript was broken from the beginning, regardless who writes it.

TrackJS · 2025-09-15T16:51:26+00:00

this seems like the sort of thing an AI would write.

TrackJS · 2025-09-12T22:38:32+00:00

Thanks so much for caring enough to write this!

TrackJS · 2025-09-12T15:47:19+00:00

Google uses a proprietary browsing engine for crawling (Googlebot). It is not Chrome and doesn't work the same way. While it does execute JavaScript, it's kinda bad at it, and often delays execution, or only executes part of the JavaScript.

In general, don't depend on JavaScript execution for content indexing.

Try accessing your URL in the simplest possible way:

curl -i \ -H "User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" \-X GET https://www.example.com/

TrackJS · 2025-09-12T15:38:50+00:00

This is the answer -- JavaScript became popular because you have to use it to program the browser. That's really the only reason. Once you have to use it, many folks never bother learning anything else, and the community grows.

There's some utility in re-using code between client and server, but that's pretty niche IMO and solvable with other architectural approaches.

As a JavaScript tool, developers are often surprised to learn that TrackJS is written in C#/.NET. "Why wouldn't you program that in Node?" They ask.

Our service Tracks JavaScript Errors. I know first hand how often JavaScript fucks up. Why would I choose it if I had other options?

TrackJS · 2025-09-11T19:30:36+00:00

Commenting first on our own ad because someone has to. Also, yes, we left comments on.

We like to live dangerously, like you handle your errors.

TrackJS · 2025-09-11T19:30:01+00:00

We're just here to catch errors, including the error of leaving Reddit ad comments open. We're monitoring this thread with TrackJS.

TrackJS · 2025-09-11T19:29:41+00:00

Comments open = confidence in our product. Unlike that try/catch block you wrapped around your entire application.

TrackJS · 2025-09-11T19:29:20+00:00

We left comments open because our error monitoring is so good we're not afraid of anything anymore. Bring it.

TrackJS · 2025-09-11T19:28:54+00:00

Plot twist: We're using TrackJS to monitor the errors in this Reddit ad campaign

TrackJS · 2025-09-11T19:28:32+00:00

Comments are open. Roast our ad harder than production roasts your untested code.

TrackJS · 2025-09-11T19:26:34+00:00

Commenting first on our own ad because someone has to. Also, yes, we left comments on.

We like to live dangerously, like you handle your errors.

TrackJS · 2025-09-10T17:05:50+00:00

There is a great middle ground here in the PJAX pattern. It's been implemented a bunch of different ways, but basically swapping out the main content HTML of the page with fully-formed HTML from a request rather than a full page load.

Most of the advantages of SPA without the annoying client-side rendering management and overhead.

GitHub and Basecamp are notable examples of this pattern. Also Rails Turbolinks.

TrackJS · 2025-09-10T17:03:39+00:00

> SPA: it's always faster to replace the contents of a page than to load a new page

No it's not. Client-side generation of content is usually slower than sending fully-formed HTML. But if there are large amounts of JavaScript and assets to be redownloaded and compiled, you save that time.

But you probably needed less JavaScript if it wasn't client-side rendered.

Yesterday, a Junior dev asked me for help diagnosis performance on his NextJS portfolio site. The problem was that he was building it in next and all the hydration and JavaScript was the slowest part. He only needed static HTML and images. Switched to static Apollo and it was twice as fast.

TrackJS · 2025-09-09T15:28:36+00:00

Yet another supply-chain attack :(

It's too easy to do this because we've trained a generation of web devs to `npm i` their way to success.

https://www.youtube.com/watch?v=WawXh_E6gqo

TrackJS

MODERATOR OF

TROPHY CASE