Wojciech Maj

I have tested this PR and I can confirm that this fix when applied fixes the plugin on Webpack 5.

Hi! That would be super neat, although not trivial to implement. Let's keep it in the backlog!

No, at the moment React-Clock is presentational only.

Fixed by #98 @oliviertassinari

Actually, since https://github.com/jantimon/html-webpack-plugin/pull/972 html-webpack-plugin loader has `force` flag that skips the very `if()` you deleted. So it could be as easy as to add `force: true`. 🤔

Fixed in #46, waiting for merge...

This sounds like a bug I'd rather resolve than create workarounds for. Would it be possible for you to create a minimal reproduction repo or a description of how these...

Unlikely to happen, because we have no way of knowing which century we should assume. `new Date().getYear()` returns `122` at the moment of writing. So we wouldn't be able to...

What worries me more is "un-formatting" it. Like, "70" should be 1970 or 2070? How do we decide? Should we require additional `century` (number) or `parseYearToFullYear` (function) prop in this...

Not at the moment, but once the feature lands to pass unfinished ranges to onChange function, you'll be able to detect selected first date & set minDate/maxDate accordingly.