ky

Problem The hook has the following description... This hook enables you to modify the request right before retry. ... but it cannot modify request . This is because the hook receives a frozen object. Note, the current behaviour is a bit inconsistent, as is shallow. So can be mutated for instance, but not . Context My main motivation for this feature is to work around #739. In my case, some users are behind middleboxes that don't support HTTP/2. I would prefer not to degrade the experience for all users (by removing completely), and only fallback where necessary. Ideally if could be modified, I could do something like this... I currently use a that wraps to achieve a similar outcome, but its quite complex. Proposal In and , pass the live options to the hooks, as we do with ... This would allow the hook to adjust the options uses for the next attempt. I'd be happy to contribute a PR if this change would be something you'd like to support. Alternatives Another option could be for to support this fallback behaviour internally, but I figured it would probably be useful for to be modifiable on retry like the rest of the request.

is , and CI runs it across a three-version Node matrix, with in each job. Measured on run 35139889608, Node 24 job, macos-latest: From that job's log: 1057 tests, of which the browser tests are 113s of AVA's reported time across 59 tests, against 428s for everything else. The browser tests drive ky in chromium, firefox and webkit, so the runner's Node version is not the variable. The same holds for , the build, and the test typecheck. All of it runs three times. Running the browser tests and the static checks once, with the matrix covering only the Node-side tests, would remove two of the three Playwright installs and two thirds of the browser work. Happy to send a PR, or to drop it if keeping the workflow identical across your repos is worth more than the minutes.

The option (Node.js/undici-specific) was being lost because it was listed in , which prevents options from being passed separately to . However, is a fetch-only option that the constructor doesn't accept. It must be passed directly to . Similarly, the option is also fetch-only in many environments. Fixes #687