Glen Mailer

> Ready for review? I'm happy to take notes on this, but i'm not intending to merge until the fix (or an equivalent) to #394 is included - and I...

The fix will be released when what changed in webpack 5 is understood and then a fix can be developed. If anyone is waiting on this and wants to help,...

If/when I get time to poke at this a little deeper, my plan would be to: - using the example project on webpack 4, run through the main scenarios for...

I spent a little time understanding what the remaining outstanding issue is - it does appear to be a change in webpack core, so I'm going to try and produce...

There's been a few reports of webpack 5 issues, but I haven't had time to look into them. None of my active projects currently use hot-middleware, so this isn't a...

> I combined the 2 PR's that fix webpack 5 bugs on my forked master branch, feel free to use it in npm Thanks for doing this! I'm intending to...

The latest state of webpack 5 support is that no-one has yet taken the time to understand what has actually changed and why that has caused a problem. Once that...

This isn’t my area of expertise, but I will happily merge a PR from someone who knows what they’re doing here. I suppose it should be something slightly off-white to...

I was also looking into something like this, we've got a fairly long SQL file that contains lots of CRUD queries that end up repeating the same list of fields....

That plugin is only needed for webpack v1. The plugin itself had a spelling error in its name.