Phil Bates

I just hit this as well on Node 14, kinda confusing to explain... I had a webpack plugin that has punycode v2 as an explicit dependency so v2 was the...

+1 This would be an excellent feature.

@dangreen I'm not sure if this is entirely the same issue, but I'm getting unexpected version matching with Safari, I think due to it using the iOS version instead of...

Thanks @dangreen that did indeed fix my issue. Although I will say that I was confused because assumed that the `ios_saf` query is supposed to relate to the **Safari** version,...

laravelcollective/html is now [abandoned](https://laravelcollective.com/thanks), and there's no guarantee that it will be updated to support Laravel 11, at the moment it is fixed to support up to Laravel 10 only...

> I would probably fork it Someone [forked it](https://github.com/LaravelCollective/html/issues/741#issuecomment-1567557746) already which is published at https://github.com/LaravelLux/html - though there's nothing to say that that fork will become the "official fork" or...

@rudiedirkx that makes sense. For context, in our project we use both this package as well as laravelcollective/html directly in hundreds of places, so as this package also pulls in...

@rudiedirkx so you're saying that we don't need to update this laravel-form-builder package's composer.json to require the fork, instead it is up to us in each project's composer.json to require...

Looks good to me, thanks @rudiedirkx!

+1 This would be a very useful addition.