apify / apify-docs

This project is the home of Apify's documentation.
https://docs.apify.com
Apache License 2.0
26 stars 71 forks source link

Uncaught runtime errors overlay during local development in Firefox #1025

Open honzajavorek opened 3 months ago

honzajavorek commented 3 months ago

Runnning docs locally, I get these. It's something I see right after a fresh git pull, npm i, npm start install. The site works ok if I dismiss the overlay, but it consistently pops up in my Firefox @ macOS. Pops up even with all add-ons turned off. Doesn't pop up in Safari.

As a webpack noob I don't know what could be wrong, also I don't know if this is specific to my machine or anyone else with Firefox experiences the same.

Screenshot 2024-05-21 at 13-15-11 Apify Documentation(1)

mtrunkat commented 3 months ago

@B4nan could you take a look?

B4nan commented 3 months ago

I can take a quick look, but I would surely not consider this as a priority as its dev only issue with FF.

B4nan commented 3 months ago

spent ~5 minutes clicking in firefox and nothing happened...

B4nan commented 3 months ago

Maybe it's connected to making changes to the documents you see, hard to guess, but its most likely not in our code really...

My guess is its some docusaurus bug, I wouldn't bother with this more before we move to docusuarus v3, we are quite behind with updates these days. There are more things like #952 which will require the update (since v3 does the anchor checks automatically).

honzajavorek commented 3 months ago

Cool, no problem. I don't deem it priority either, as I wrote, the site works and this is merely an annoyance. If I happen to figure out the root cause, I'll share it here, but I won't spend much energy on it. Thanks @B4nan for verifying on your device, this makes me think it can be even something with my own setup (even though it didn't appear in April).

TC-MO commented 3 months ago

I think I catch those sometimes when I'm switching branches when I have docs running locally, but usually refreshing works.

I'm also on FF, but saw it a few times on Chrome as well.