rsnext/packages
Steven 78dc2db916
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`.
2024-07-01 08:10:35 -07:00
..
create-next-app v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
eslint-config-next v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
eslint-plugin-next v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
font v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next fix(next/image): improve query string validation for integers (#67293) 2024-07-01 08:10:35 -07:00
next-bundle-analyzer v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next-codemod v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next-env v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next-mdx v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next-plugin-storybook v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next-polyfill-module v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next-polyfill-nomodule v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
next-swc v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
react-refresh-utils v15.0.0-canary.49 2024-06-29 23:22:57 +00:00
third-parties v15.0.0-canary.49 2024-06-29 23:22:57 +00:00