next.js

78dc2db9 - fix(next/image): improve query string validation for integers (#67293)

fix(next/image): improve query string validation for integers (#67293) The Image Optimization API currently uses `parseInt()` for `w` and `q` query string parameters. This doesn't handle floats as you might expect and instead coerces, for example `parseInt('99.9') === 99`. This PR changes the runtime to match the build time validation and only accept integers for `w` and `q`.