Spring Sale! Save 15% on WordPress books with code: SPRING22
Web Dev + WordPress + Security

Replacement for JavaScript Errors Notifier (Chrome Extension)

Heads up about the JavaScript Errors Notifier extension for Google Chrome. Looks like it was removed from the Chrome store sometime last year. Not sure of the reason behind it, but can tell you that currently there are no suitable extensions to replace it. Kinda sucks because JavaScript Errors Notifier was one of my favorite “always on” extensions. It makes it easy to spot any JavaScript errors as you develop, design, or browse the Web. Fortunately there’s still a way to use this extremely useful extension..

For those not familiar, here is a quick screenshot that shows how it works:

JavaScript Errors Notifier showing errors on a website (click to view full-size image)

Notice the little red icon next to the browser’s address bar. If the current web page does not have any JavaScript errors, it is greyed out. If the page does have any errors, the little icon displays red. Then if you click on the icon, it pops up a little dialogue with specific details about each error. Again, super useful for web developers and anyone who wants to keep an eye on things.

No suitable alternatives (yet)

I’m hoping that this post will bring attention and “inspire” someone to pick up development or fork the JavaScript Errors Notifier addon. Currently there are no suitable alternatives for Chrome. So it falls into the “one of a kind” and “virtually priceless” categories.

To be fair, there are a couple of other “JavaScript notifier” type plugins available for Chrome, but they don’t really inspire a lot of confidence:

You can check those out if you’re feeling brave, but for me there’s too many red flags to take seriously. The original, now-removed JavaScript Errors Notifier extension had many, many users, and many great reviews.

Firefox? JavaScript Errors Notifier add-on is still available for Firefox :)

So what to do? As a web developer, I can use the browser’s code inspector to really dig in and examine JavaScript (and other) errors on any web page. BUT as a regular human just browsing the Web, there is no way to monitor JS errors “as you surf”. I manage many web pages, and surfing around pages is one way that I keep an eye on things, catch errors, and so forth. Thanks to the JavaScript Errors Notifier extension, I’ve caught a lot of errors that otherwise would have been missed.

The good news? JavaScript Errors Notifier is still available on GitHub :)

Replace with unpacked extension

JavaScript Errors Notifier is developed by Sergey Barbushin. It’s currently available as a free Firefox add-on. For Chrome, the extension was available for several years at the Chrome Web Store via the following URL:

https://chrome.google.com/webstore/detail/javascript-errors-notifie/jafmfknfnkoekkdocjiaipcnmkklaajd

That’s now a 404 Not Found, sadly. The good news is that the source code for the extension remains available at GitHub. So for now at least, it’s still possible to run JavaScript Errors Notifier as an “unpacked” extension. This may change in the future, but for now it works great. Here’s how to set it up in a couple of minutes:

  1. Download the extension (ZIP file) via GitHub
  2. Unzip the file to get the extension folder, /javascript-errors-notifier/
  3. Move the folder to a permanent location (e.g., /Applications/ on macOS)
  4. Open Chrome browser, in the address bar visit chrome://extensions/
  5. Click to toggle “Developer mode” (upper-right corner)
  6. Click “Load unpacked” from the top menu buttons
  7. Choose the extension folder, /javascript-errors-notifier/
  8. Click “Select” and done.

After selecting the folder, it immediately will appear among your other extensions:

JavaScript Errors Notifier running locally (click to view full-size image)

I’ve been running the extension this way for a couple of weeks and it’s working beautifully. A few notes to keep in mind:

  • The extension will break if you move the folder after install
  • After installing, you can check for errors by clicking the “Errors” button
  • At this time, there is only one error: “Manifest version 2 is deprecated, and support will be removed in 2023.” Not a huge deal really.

Hopefully, the extension author will jump back in and continue development. If not, then eventually it will no longer work, have bugs, etc. But for right now, running the extension locally/unpacked works great. Maybe it will buy enough time for some alternate JavaScript-notifier extensions to hit the scene.

A lot of people use this extension, so hopefully someone will pick it up, fork, or whatever is needed to keep it alive and awesome.

Keep me posted If you know of any alternative for JavaScript Errors Notifier, or if you know of any new developments with the original version, please let me know so I can update this article. Thanks!

Jeff Starr
About the Author
Jeff Starr = Web Developer. Book Author. Secretly Important.
WP Themes In Depth: Build and sell awesome WordPress themes.

One response to “Replacement for JavaScript Errors Notifier (Chrome Extension)”

  1. Jim S. Smith 2022/04/14 12:52 pmReply

    Yeah.

    As usual,

    Seems that many of these “big projects” are doing away with a lot of useful features that many developers make heavy use of! Such a shame that they make all these radical decisions, without actually seeing how much of their user-base may use these features.

    My biggest complaint about FireFox – was just THIS sort of behavior. They removed so many useful features that I used quite frequently like: Viewing the contents of cookies, being able to import my crafted search-engine plugin XML files (for testing before submission), backing up search-engine plugins (a BIG ouch when removed), and several other features!

    I don’t expect GOOGLE, MOZILLA, and other “big projects” to cease this one-sided decision-making anytime soon, either.

    This is exactly one of the major reasons why there are many alternative projects cropping up everywhere, to include an alternate to WordPress. I LOT of people are very upset that WordPress is forcing “Gutenberg editor” upon everyone – and increasing the serious “codebase bloat” in the process.

    It’s only going to get worse, I’m afraid – as the “big-company mentality” sets in for the long haul. We, the users, are just “numbers” and nothing more.

    Always happy to see workable alternatives presented, though.

    – Jim S.

Leave a reply

Name and email required. Email kept private. Basic markup allowed. Please wrap any small/single-line code snippets with <code> tags. Wrap any long/multi-line snippets with <pre><code> tags. For more info, check out the Comment Policy and Privacy Policy.

Subscribe to comments on this post

Welcome
Perishable Press is operated by Jeff Starr, a professional web developer and book author with two decades of experience. Here you will find posts about web development, WordPress, security, and more »
USP Pro: Unlimited front-end forms for user-submitted posts and more.
Thoughts
Coding never ends. Bring a snack.
Not posting anything online usually means I’m busy working on my next project.
Today is my 50th B-day :)
Deep in the code.
Making good progress on my next pro plugin, Simple Ajax Chat Pro :)
Events definitely are speeding up. For those who are paying attention.
New wave of spam comments easily blocked, add =https:// to WP Discussion settings ▸ Disallowed Comment Keys.
Newsletter
Get news, updates, deals & tips via email.
Email kept private. Easy unsubscribe anytime.