Clicking nodes results in JS error

In both Chrome and Firefox, I am getting the below stack trace when trying to click any nodes (found via node hunter):

node_hunter.js:168 Uncaught TypeError: Cannot read properties of undefined (reading 'setLngLat')
    at Map.<anonymous> (node_hunter.js:168:39)
    at Map.p (map.js:1523:30)
    at (evented.js:130:26)
    at (map_event.js:56:19)
    at th.handleEvent (handler_manager.js:346:58)
    at bi.___hb (browser.js:272:37)

Thanks for reporting this!
I accidentally broke that in my behind-the-scenes efforts on Club / Crew / Group / Team

It’s fixed up now - sorry for the trouble!

1 Like

Do you have a mechanism in place to automatically send telemetry back to you when there are javascript errors like this? If not, it could be a great way to find out even faster about problems like this.

I do, but it’s SO NOISY :confounded: that it’s completely unusable.

I’m either the worst JavaScript developer or this tooling is just a complete dumpster fire.
Like … what do I do with 1.7k instances of “Failed to fetch” in a js file that I don’t own :person_facepalming: and, go figure, I can’t find your particular TypeError at all :sob:

Here’s one from the Greatest Hits

UnhandledPromiseRejectionWarning: TypeError: Load failed
unknown  0  ?(...)
unknown:0:in `?'


(The fix is out, btw)

Edit: Just in case, my harsh tone is directed squarely at the horrible JS error catching situation (or my terrible implementation of it? somehow?), not at you or your helpful suggestion … apologies if my tone was off-putting.

Haha, no worries. I get it :slight_smile:

I just got prompted to refresh the page, and can once again click on nodes. Thanks for the rapid response!