F4RAN/cuimp-ts

AI Summary: The user requests a new `proxy` option to be added to the `CuimpOptions` interface. This feature would allow all HTTP requests made within a session to automatically use the specified proxy, similar to how the `cookieJar` option functions. The goal is to avoid configuring a proxy for each individual request.

AI Summary: The user is requesting two enhancements for the cuimp system: the ability to suppress console.log and debug messages to avoid interference with custom loggers, and an option for advanced users to disable the automatic download of binaries, allowing for custom installation control.

AI Summary: The issue describes a bug where setting a custom `Accept: application/json` header results in two `Accept` headers being sent in the HTTP request. This is due to a default `Accept` header in `curl_chrome.bat` that is not being overridden when a custom header is provided, leading to unexpected behavior and difficulties in controlling the `Accept` header.

AI Summary: The user is encountering an 'UNSUPPORTED_PROTOCOL' error when trying to execute a curl command on Windows. The error appears in two scenarios: one where the path to the binaries contains spaces, and another where the path is clean but the error message suggests a missing URL and that the system cannot find the path. The user suspects path or quoting issues.

AI Summary: The user is encountering an issue where cuimp does not return the HTTP response body for 4xx/5xx errors, only a CurlError. They are seeking a way to configure cuimp to provide the full response (status, headers, body) even in error cases, similar to Postman or Axios.

AI Summary: The user is encountering a 404 Not Found error when attempting to download the `curl-impersonate` binary for Windows. This indicates that the specified download URL for the binary is incorrect or the file is missing from the releases page.