StringEpsilon

@aarowman: 5.0.0 is a rewrite and not intended to be compatible with 4.x. See the release notes and #811. `connected-react-router` will have to make changes in order to be compatible...

The license file is provided with the package. That should be sufficient for the MIT in terms of publishing a work on NPM. 4.10.1: https://unpkg.com/browse/[email protected]/LICENSE 5.0.0: https://unpkg.com/browse/[email protected]/LICENSE If you bundle...

https://github.com/ReactTraining/history/issues/505 I'm not sure if this will get a fix in history 4 (because it's a breaking change). But it has been fixed in history 5.

History 5 is not compatible with react router 5. You can try the react router 6 beta, but that is still a beta and comes with it's own set of...

[As per the docs](https://github.com/ReactTraining/history/blob/v4/docs/Blocking.md): The blocking only affects what history can register and properly intercept - and only on the transition between locations. With your particular situation, the initial location...

You'll notice that both the issue and the PR were closed by the person who filed them - not the maintainers. The lock was simply done by Stalebot. And yeah,...

This was an intentional change in v5. You can read the details in #551 and #516. I forgot to mention that in my unofficial breaking changes documentation: #811

I just found a very easy way to provoke the leaky behavior: 0. Open VS Code on any C# project. 1. Open any C# file. 2. Make *any* change to...

Some additional observations: Memory utilization does actually go down, if you let VS Code sit long enough without interacting with it. But this is on the scale of hours, not...

To provide some actually useful info instead of just repeating that the issue exists (🙃): Since opening the issue, the leak has become less severe. It still leaks and can...