@pablosichert thank you so much for this component! It is extremely useful and I've found it more reliable than other options 👍 I'm sure you're quite busy but hopefully you'll have some time to merge this simple PR so it is integrates with testing suites without mocks

Hey there! Sounds fair enough to include that check.

I'm still curious when that happens, could you elaborate?

@pablosichert Sure thing! It was occurring when running Jest / Storybook tests, likely due to its use of JSDOM instead of a real browser environment. There's probably a way to create a mock or workaround for this issue, but having this simple check makes it easier to integrate for everyone using it without those added steps

Additionally I've seen the same Cannot read property 'parentNode' of undefined error emitted by this source in the console from time to time when visiting a different page in a Next.js app.

If it only happened for the tests, I would have considered to detect that at instantiation.

But with the risk of it happening at runtime, applying the check there seems like the better option.

Thank you for the PR!

@pablosichert No problem! Thank you for the quick review and merge!