가전청소 | GitHub - Sindresorhus/ky:

이름 : Tory

이메일 : toryacuna727@gmail.com

얀락처 : MI

청소날짜 :

청소주소 :

Sindre's open supply work is supported by the community. Ky targets modern browsers, Node.js, Bun, and Deno. It's just a tiny package deal with no dependencies. This readme is for the next model of Ky. For the current model, click right here. If you're utilizing Deno, import Ky from a URL. The input and choices are the identical as fetch, with extra choices accessible (see below). Returns a Response object with Body methods added for comfort. So you may, for instance, call ky.get(input).json() instantly without having to await the Response first. When known as like that, an appropriate Accept header will probably be set depending on the physique technique used. Available body shortcuts: .json(), .textual content(), .formData(), .arrayBuffer(), .blob(), and .bytes(). The .bytes() shortcut is only current when the runtime helps Response.prototype.bytes(). ⌨️ TypeScript: Accepts an elective kind parameter, which defaults to unknown, and is passed by means of to the return type of .json(). This throws a SchemaValidationError when validation fails. Sets choices.methodology to the tactic title and makes a request.

⌨️ TypeScript: Accepts an non-obligatory kind parameter for use with JSON responses (see ky()). Same as fetch enter. When using a Request instance as enter, any URL altering choices (such as baseUrl) can be ignored. HTTP technique used to make the request. Internally, the standard methods (GET, Post, PUT, armistice PATCH, HEAD, DELETE, and Query) are uppercased in an effort to keep away from server errors attributable to case sensitivity. Shortcut for sending JSON. Use this as an alternative of the physique possibility. Accepts any plain object or value, which can be stringified utilizing JSON.stringify() and sent within the physique with the right header set. Search parameters to include within the request URL. Setting it will merge with any existing search parameters in the enter URL. Accepts any value supported by URLSearchParams(). When passing an object, setting a value to undefined deletes the parameter, whereas null values are preserved and transformed to the string 'null'. A base URL to resolve the enter in opposition to. When the input (after applying the prefix choice) is barely a relative URL, similar to 'users', '/users', or '//my-site.com', it is going to be resolved in opposition to the baseUrl to determine the destination of the request.

Otherwise, the input is absolute, corresponding to 'https://my-site.com', and it'll bypass the baseUrl. Useful when used with ky.prolong() to create niche-specific Ky instances. If the baseUrl itself is relative, it will likely be resolved towards the atmosphere's base URL, akin to document.baseURI in browsers or location.href in Deno (see the --location flag). Tip: When setting a baseUrl that has a path, we recommend that it include a trailing slash /, as in '/api/' slightly than /api. This ensures more intuitive conduct for web page-relative input URLs, reminiscent of 'users' or './users', the place they will lengthen from the complete path of the baseUrl somewhat than changing its final path phase. A prefix to prepend to the input earlier than making the request (and earlier than it's resolved towards the baseUrl). It may be any legitimate path or URL, either relative or absolute. A trailing slash / is optionally available and will be added routinely, if wanted, when it is joined with input. Only takes effect when input is a string.

Useful when used with ky.extend() to create niche-specific Ky situations. Normally, you should use the baseUrl possibility as an alternative, as it is extra per web standards. However, prefix is helpful if you need origin-relative input URLs, reminiscent of /users, to be treated as in the event that they had been web page-relative. In other phrases, the main slash of the enter will primarily be ignored, as a result of the prefix will grow to be part of the input earlier than URL resolution happens. The prefix and enter are joined with a slash /, and slashes are normalized at the join boundary by trimming trailing slashes from prefix and main slashes from input. After prefix and input are joined, the result is resolved against the baseUrl option, if current. Controls retry conduct. Each discipline is documented individually below. If retry is a number, it will be used as restrict and other defaults will remain in place. Network errors (e.g., DNS failures, connection refused, offline) are routinely retried for retriable methods.

Only errors recognized as network errors are retried; different errors (e.g., programming bugs) are thrown instantly. Use shouldRetry to customize this behavior. 413 Payload Too Large is just retried when the response features a retry timing header. When the response status is contained in both statusCodes and afterStatusCodes, Ky uses retry timing headers to decide on the retry delay. Retry-After may provide a delay in seconds or an HTTP-date. If Retry-After is missing, Ky falls back to price-restrict timing headers (RateLimit-Reset, X-RateLimit-Retry-After, X-RateLimit-Reset, and X-Rate-Limit-Reset). Numeric Retry-After and X-RateLimit-Retry-After values are interpreted as delay seconds. Numeric RateLimit-Reset, X-RateLimit-Reset, and X-Rate-Limit-Reset values may also be interpreted as present-period Unix timestamps. If the status code will not be in afterStatusCodes, retry timing headers shall be ignored. If the retry delay from a retry timing header is greater than maxRetryAfter, Ky will use maxRetryAfter. The backoffLimit choice is the upper limit of the delay per retry in milliseconds.