Jérémie van der Sande

I think we can safely use this snippet. If an environment does not support writing properties to `window.history`, the patching wouldn't work in the first place anyway :)

Hi @HansBrende :) In the end I never followed up on this after opening the initial issue. It has not proven a big problem in my production environment yet. Definitely...

Thinking about @molefrog's comment on window.history mutability, I guess the simplest workaround would be to store the "symboled" entry... On `window` itself. At least we're sure it's mutable everywhere

For the major + minor version... Is it really wise? In the main use case I see (Independent microfrontends), minor version can easily drift, and in some cases, major version...

CI tests are failing, but they seem to also be failing on the `next` branch unmodified, at the same point, so this doesn't seem to be linked to those changes.