Kamil Kollman

@gcattan is it possible to observe History and Location outside of mobx router?

No problem about the delay! Thank you for your suggestion, but it has an important caveat - I intend to use History and Location outside of the component. I have...

> Unfortunately, I was not able to reproduce your bug this morning on my local machine. That's a bummer. I am using the same versions of Vite, node and yarn,...

@gcattan Sorry I am calling you once again, but I have been using mobx-react-router for years and it would be a shame to drop it because of the React Router...

@gcattan Thank you! It seems, however, that this approach isn't too stable - any reinstall causes further issues. At some point I experienced new bug: `Transforming JavaScript decorators to the...

@gcattan thank you! 🫡 ❤️ I can confirm installation works well and you can start app with no problem. The only caveat is that the router store, when initiated on...

Thanks! I tried a couple of approaches based on your answer. I eventually used `createBrowserHistory` instead of memory history, and I can see the url change and the observed location...

Good point. That being said, with approach you suggested, react is re-rendering endlessly, perhaps that's something nested deeper in my App. Removing `observer` the component where Router is placed helps...

Okay, I can finally say: done! 🎉 The last missing puzzle was to properly configure vite.js plugins. Now I can say your solution is fully working :) Thank you very...

It looks good - in the docs I would also recommend adding some info on vite plugins to enable `@decorators`, since not all mobx users will have them added out...