Rare error in solid-app-router that I am seeing in Sentry

[fireph]

There is this relatively rare error I am seeing pop up in Sentry and was wondering if you could take a look:

TypeError N.composedPath is not a function

../../node_modules/solid-app-router/dist/routing.js in D at line 286:23

                evt.metaKey ||
                evt.altKey ||
                evt.ctrlKey ||
                evt.shiftKey)
                return;
            const a = evt
                .composedPath()
                .find(el => el instanceof Node && el.nodeName.toUpperCase() === "A");
            if (!a)
                return;
            const isSvg = a instanceof SVGAElement;

[rturnq]

Hmm, composedPath is a widely supported property of the Event interface so this feels like Sentry is interfering. They replace addEventListener on the various event target prototypes with their own. Since you indicated it doesn't always happen, I wonder if there is a race condition between the router and Sentry and somehow the router's event handler gets the event object destined for their wrapper.

Does this come up in a development build with HMR or production-type builds?

[ryansolid]

Closing as stale.