steinarb

This stack overflow answer from April 9 2022 is interesting https://stackoverflow.com/a/71812298 The stackoverflow answer says: "I had this error because Vite was bundling two copies of the same version of...

I searched for react-router on the vite github discussions and fond this topic: https://github.com/vitejs/vite/discussions/13390 I found this reply https://github.com/vitejs/vite/discussions/13390#discussioncomment-6174166 saying "I guess you need to add react-router and react-router-dom to...

Started a topic in vite discussions https://github.com/vitejs/vite/discussions/20180

The `useLocation() may be used only in the context of a component` problem is still present when building with vite 7.x.x. I have tried building apps using redux-first-history with vite...

@lprimak This is probably an issue for me too, but not related to the classloader issue mentioned earlier (probably the next thing I will run into once the classloader issue...

I got this error too after upgrading to debian 13 "trixie" (on amd64): ``` Warning: https://dbeaver.io/debs/dbeaver-ce/InRelease: Policy will reject signature within a year, see --audit for details Audit: https://dbeaver.io/debs/dbeaver-ce/InRelease: Sub-process...

Signing the repo with something stronger than SHA1 seems the obvious fix...?

FWIW I am now using react-router 7.1.1 and both navigation with push and location detection with LOCATION_CHANGE seems to work for me...?

Can the problems with HistoryRouter wrapper be the cause for this problem? https://github.com/salvoravida/redux-first-history/issues/137 (The react-first-history router stopped being recognized as a router when I bumped the vite version to 6)

Still an issue in the current version of the app on android