Glenn Rempe

Wondering if you have any thoughts on this now that its been narrowed down with a working bug example.

Hi. Clearly, as you say, there is a conflict between the tailwind forms plugin and DaisyUI. It took multiple hours of effort and communication with you to identify that and...

Thanks for hearing me out. I think the most important thing is to document known conflicts. Yes, perhaps breakage could occur in combination with other tools, but in this case...

I came here for exactly this issue as well. Requests to `https://www.mydomain.com/proxy/api/event` are throwing a 431 error. Also Next.js app using `auth0/nextjs-auth`

If @4lejandrito could engage here it would be helpful. I have been in direct contact with the leadership at Plausible and @vinibrsl is one of their engineers who is working...

I can confirm that @vinibrsl has made a change to the default header size that was being accepted server side at Plausible. This resolved the 431 request errors for me....

This is a very helpful command, but it is marred by this issue. The Usage and Commands data that is inserted needs to be configurable to work with different semantic...

This is a pretty major bug IMHO that will bite any user that types anything other than a number in response. Would be great if this could be addressed since...

This would be very helpful. For example, other machines in my household were shared at one point and have apps installed from more than one account which makes installing upgrades...

I also agree that bumping version in the working dir without committing that change is not the right flow. Yarn publish should require a clean working dir if in git...