Mark Bakhit

The `whitenoise` maintainers have largely been MIA, so I went ahead and forked it into my own package [ServeStatic](https://github.com/Archmonger/ServeStatic). This PR is no longer blocked.

Ooohh! it's very good to hear that meta is pushing server side components forward. That would vastly simplify integrating it with ReactPy.

Related issue: #525

I ended up developing a [robust reconnecting websocket](https://github.com/reactive-python/reactpy-django/blob/c80f94dca4768eed3e85000a76eb8037a705ec2c/src/js/src/utils.ts#L1) within ReactPy-Django that can be ported over to ReactPy core identically. The websocket can be [configured within Python](https://reactive-python.github.io/reactpy-django/latest/reference/settings/#stability-settings) via settings.

It's been a while since these type hints have been broken, but if I recall they broke due to some type hinting restrictions that cropped up. The issue was that...

No, `key` can be any serializable value. That includes integers and some objects like `UUID`.

Played around with this for a bit... I'm not seeing a way to fix this without changing our component interface. Kind of upsetting that there are so many Python type...

Mypy flags `key` as an invalid keyword with the latest implementation in your branch. 

I've [created a post](https://discuss.python.org/t/type-hints-for-kwarg-overrides/47196) over at the Python typing forums to see what the sentiment is around fixing this type hinting limitation.

Marking this as a draft since it's broken with most linters.