Does anyone know why larger repositories take ages to spin up their deployment build with @vercel ? the actual build step doesn't even start until 15-20 minutes in....
Obscure bug of the week: Users were unable to upload to S3 in Firefox.
Turns out, the FormData boundary had a different ID between the header and the body and S3 reported "truncated data".
The fix? Upgrading to v4.46.2 of rollup: github.com/rollup/rollup/pul… (4.46.1 seems broken?)
To us, this once again showed the importance of true Cross-Browser E2E testing as none of our existing tests caught this. We're already in the process of adding more systems to prevent 3rd party dependencies breaking final build, but this was a tough one!
A bit of a PSA; but for anyone using @vercel to host their site, and has customers reporting white, blank pages: so far it's only ever been people that were using @NordVPN.
Once the VPN was turned off, the sites were available again.
Ever had the query builder's chunk() method skipping rows when you used where-clauses while the callback is updating your model?
Add this little macro and replace "chunk" with "chunkSimple":
gist.github.com/spaceemotion…#laravel#laracon#eloquent
Had this on my whishlist for quite a while, glad I got it. Can't wait to try it out :) Good luck with your game #BeeBeeQ! x.com/popupAsylum/status/851…