@helia/verified-fetch 0.0.0-28d62f7 → 0.0.0-2d965be
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/index.min.js +7 -7
- package/dist/src/utils/responses.d.ts +0 -1
- package/dist/src/utils/responses.d.ts.map +1 -1
- package/dist/src/utils/responses.js +0 -6
- package/dist/src/utils/responses.js.map +1 -1
- package/dist/src/verified-fetch.d.ts.map +1 -1
- package/dist/src/verified-fetch.js +8 -38
- package/dist/src/verified-fetch.js.map +1 -1
- package/package.json +17 -19
- package/src/utils/responses.ts +0 -7
- package/src/verified-fetch.ts +9 -50
package/README.md
CHANGED
|
@@ -351,7 +351,7 @@ console.info(obj) // ...
|
|
|
351
351
|
|
|
352
352
|
The `Accept` header can be passed to override certain response processing, or to ensure that the final `Content-Type` of the response is the one that is expected.
|
|
353
353
|
|
|
354
|
-
If the final `Content-Type` does not match the `Accept` header, or if the content cannot be represented in the format dictated by the `Accept` header, or you have configured a custom content type parser, and that parser returns a value that isn't in the accept header, a [406: Not
|
|
354
|
+
If the final `Content-Type` does not match the `Accept` header, or if the content cannot be represented in the format dictated by the `Accept` header, or you have configured a custom content type parser, and that parser returns a value that isn't in the accept header, a [406: Not Acceptible](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/406) response will be returned:
|
|
355
355
|
|
|
356
356
|
```typescript
|
|
357
357
|
import { verifiedFetch } from '@helia/verified-fetch'
|