Dmitriy Bryokhin

Hi! This is very interesting... I have tried your example, and it works fine when I remove StrictMode in `index.js`. Apparently it has something to do with this. I will...

I have tried Strict mode in our App example and it works fine, however I've found that it doesn't work when I use: ``` import { createRoot } from 'react-dom/client';...

Something is weird with this new `createRoot` + `StrictMode`. It is only reproducable with this combination. Works fine with the old `ReactDOM.render`, and works fine without `StrictMode`. I've made even...

I think the problem mostly lies in this new "createRoot", so unless you need some specific features from it, I would skip it for now. However if you don't need...

Thanks! Nice find, I will watch it and see if it helps. Ohh, time to dive deeper in React v18 😃

Hello! This issue should be now fixed in v1.1.0 🎉 We are using new `useEffectOnce` hook to avoid the "double mount" that is coming from the React v18 StrictMode.

Hello! I have made similar changes and it's already available in the v1.1.0: https://github.com/NoriginMedia/Norigin-Spatial-Navigation/releases/tag/v1.1.0 I have used a bit different `useEffectOnce` hook that also accounts for the unmount cleanup effects:...

Thanks for the contribution anyways! I have also applied the TS fixes, somehow it got missed during the "build" command and got published like this. ESLint didn't detect them either...

Linking with #83 and #97

Hi, Yes, we have been thinking on some solutions for this as sometimes we also encounter this problem. However it is not always easy because sometimes the focus is not...