@helia/verified-fetch 0.0.0-7a7c0c1 → 0.0.0-7c3ce21
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 +238 -6
- package/dist/index.min.js +4 -4
- package/dist/src/index.d.ts +222 -4
- package/dist/src/index.d.ts.map +1 -1
- package/dist/src/index.js +219 -4
- package/dist/src/index.js.map +1 -1
- package/dist/src/types.d.ts +2 -0
- package/dist/src/types.d.ts.map +1 -0
- package/dist/src/types.js +2 -0
- package/dist/src/types.js.map +1 -0
- package/dist/src/utils/dag-cbor-to-safe-json.d.ts +7 -0
- package/dist/src/utils/dag-cbor-to-safe-json.d.ts.map +1 -0
- package/dist/src/utils/dag-cbor-to-safe-json.js +37 -0
- package/dist/src/utils/dag-cbor-to-safe-json.js.map +1 -0
- package/dist/src/utils/get-content-disposition-filename.d.ts +6 -0
- package/dist/src/utils/get-content-disposition-filename.d.ts.map +1 -0
- package/dist/src/utils/get-content-disposition-filename.js +16 -0
- package/dist/src/utils/get-content-disposition-filename.js.map +1 -0
- package/dist/src/utils/get-e-tag.d.ts +28 -0
- package/dist/src/utils/get-e-tag.d.ts.map +1 -0
- package/dist/src/utils/get-e-tag.js +18 -0
- package/dist/src/utils/get-e-tag.js.map +1 -0
- package/dist/src/utils/parse-url-string.d.ts +7 -1
- package/dist/src/utils/parse-url-string.d.ts.map +1 -1
- package/dist/src/utils/parse-url-string.js +6 -0
- package/dist/src/utils/parse-url-string.js.map +1 -1
- package/dist/src/utils/responses.d.ts +4 -0
- package/dist/src/utils/responses.d.ts.map +1 -0
- package/dist/src/utils/responses.js +21 -0
- package/dist/src/utils/responses.js.map +1 -0
- package/dist/src/utils/select-output-type.d.ts +12 -0
- package/dist/src/utils/select-output-type.d.ts.map +1 -0
- package/dist/src/utils/select-output-type.js +147 -0
- package/dist/src/utils/select-output-type.js.map +1 -0
- package/dist/src/verified-fetch.d.ts +17 -25
- package/dist/src/verified-fetch.d.ts.map +1 -1
- package/dist/src/verified-fetch.js +220 -143
- package/dist/src/verified-fetch.js.map +1 -1
- package/package.json +25 -15
- package/src/index.ts +223 -4
- package/src/types.ts +1 -0
- package/src/utils/dag-cbor-to-safe-json.ts +44 -0
- package/src/utils/get-content-disposition-filename.ts +18 -0
- package/src/utils/get-e-tag.ts +36 -0
- package/src/utils/parse-url-string.ts +17 -2
- package/src/utils/responses.ts +22 -0
- package/src/utils/select-output-type.ts +166 -0
- package/src/verified-fetch.ts +251 -153
package/dist/src/index.d.ts
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
*
|
|
4
4
|
* `@helia/verified-fetch` provides a [fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)-like API for retrieving content from the [IPFS](https://ipfs.tech/) network.
|
|
5
5
|
*
|
|
6
|
-
* All content is retrieved in a [trustless manner](https://www.techopedia.com/definition/trustless), and the integrity of all bytes are verified by comparing hashes of the data.
|
|
6
|
+
* All content is retrieved in a [trustless manner](https://www.techopedia.com/definition/trustless), and the integrity of all bytes are verified by comparing hashes of the data. By default, CIDs are retrieved over HTTP from [trustless gateways](https://specs.ipfs.tech/http-gateways/trustless-gateway/).
|
|
7
7
|
*
|
|
8
8
|
* This is a marked improvement over `fetch` which offers no such protections and is vulnerable to all sorts of attacks like [Content Spoofing](https://owasp.org/www-community/attacks/Content_Spoofing), [DNS Hijacking](https://en.wikipedia.org/wiki/DNS_hijacking), etc.
|
|
9
9
|
*
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
34
34
|
* import { CID } from 'multiformats/cid'
|
|
35
35
|
*
|
|
36
|
-
* const cid = CID.parse('bafyFoo') // some
|
|
36
|
+
* const cid = CID.parse('bafyFoo') // some json file
|
|
37
37
|
* const response = await verifiedFetch(cid)
|
|
38
38
|
* const json = await response.json()
|
|
39
39
|
* ```
|
|
@@ -114,7 +114,7 @@
|
|
|
114
114
|
*
|
|
115
115
|
* ### Custom content-type parsing
|
|
116
116
|
*
|
|
117
|
-
* By default, `@helia/verified-fetch` sets the `Content-Type` header as `application/octet-stream` - this is because the `.json()`, `.text()`, `.blob()`, and `.arrayBuffer()` methods will usually work as expected without a detailed content type.
|
|
117
|
+
* By default, if the response can be parsed as JSON, `@helia/verified-fetch` sets the `Content-Type` header as `application/json`, otherwise it sets it as `application/octet-stream` - this is because the `.json()`, `.text()`, `.blob()`, and `.arrayBuffer()` methods will usually work as expected without a detailed content type.
|
|
118
118
|
*
|
|
119
119
|
* If you require an accurate content-type you can provide a `contentTypeParser` function as an option to `createVerifiedFetch` to handle parsing the content type.
|
|
120
120
|
*
|
|
@@ -138,6 +138,221 @@
|
|
|
138
138
|
* })
|
|
139
139
|
* ```
|
|
140
140
|
*
|
|
141
|
+
* ### IPLD codec handling
|
|
142
|
+
*
|
|
143
|
+
* IPFS supports several data formats (typically referred to as codecs) which are included in the CID. `@helia/verified-fetch` attempts to abstract away some of the details for easier consumption.
|
|
144
|
+
*
|
|
145
|
+
* #### DAG-PB
|
|
146
|
+
*
|
|
147
|
+
* [DAG-PB](https://ipld.io/docs/codecs/known/dag-pb/) is the codec we are most likely to encounter, it is what [UnixFS](https://github.com/ipfs/specs/blob/main/UNIXFS.md) uses under the hood.
|
|
148
|
+
*
|
|
149
|
+
* ##### Using the DAG-PB codec as a Blob
|
|
150
|
+
*
|
|
151
|
+
* ```typescript
|
|
152
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
153
|
+
*
|
|
154
|
+
* const res = await verifiedFetch('ipfs://Qmfoo')
|
|
155
|
+
* const blob = await res.blob()
|
|
156
|
+
*
|
|
157
|
+
* console.info(blob) // Blob { size: x, type: 'application/octet-stream' }
|
|
158
|
+
* ```
|
|
159
|
+
*
|
|
160
|
+
* ##### Using the DAG-PB codec as an ArrayBuffer
|
|
161
|
+
*
|
|
162
|
+
* ```typescript
|
|
163
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
164
|
+
*
|
|
165
|
+
* const res = await verifiedFetch('ipfs://Qmfoo')
|
|
166
|
+
* const buf = await res.arrayBuffer()
|
|
167
|
+
*
|
|
168
|
+
* console.info(buf) // ArrayBuffer { [Uint8Contents]: < ... >, byteLength: x }
|
|
169
|
+
* ```
|
|
170
|
+
*
|
|
171
|
+
* ##### Using the DAG-PB codec as a stream
|
|
172
|
+
*
|
|
173
|
+
* ```typescript
|
|
174
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
175
|
+
*
|
|
176
|
+
* const res = await verifiedFetch('ipfs://Qmfoo')
|
|
177
|
+
* const reader = res.body?.getReader()
|
|
178
|
+
*
|
|
179
|
+
* while (true) {
|
|
180
|
+
* const next = await reader.read()
|
|
181
|
+
*
|
|
182
|
+
* if (next?.done === true) {
|
|
183
|
+
* break
|
|
184
|
+
* }
|
|
185
|
+
*
|
|
186
|
+
* if (next?.value != null) {
|
|
187
|
+
* console.info(next.value) // Uint8Array(x) [ ... ]
|
|
188
|
+
* }
|
|
189
|
+
* }
|
|
190
|
+
* ```
|
|
191
|
+
*
|
|
192
|
+
* ##### Content-Type
|
|
193
|
+
*
|
|
194
|
+
* When fetching `DAG-PB` data, the content type will be set to `application/octet-stream` unless a custom content-type parser is configured.
|
|
195
|
+
*
|
|
196
|
+
* #### JSON
|
|
197
|
+
*
|
|
198
|
+
* The JSON codec is a very simple codec, a block parseable with this codec is a JSON string encoded into a `Uint8Array`.
|
|
199
|
+
*
|
|
200
|
+
* ##### Using the JSON codec
|
|
201
|
+
*
|
|
202
|
+
* ```typescript
|
|
203
|
+
* import * as json from 'multiformats/codecs/json'
|
|
204
|
+
*
|
|
205
|
+
* const block = new TextEncoder().encode('{ "hello": "world" }')
|
|
206
|
+
* const obj = json.decode(block)
|
|
207
|
+
*
|
|
208
|
+
* console.info(obj) // { hello: 'world' }
|
|
209
|
+
* ```
|
|
210
|
+
*
|
|
211
|
+
* ##### Content-Type
|
|
212
|
+
*
|
|
213
|
+
* When the `JSON` codec is encountered, the `Content-Type` header of the response will be set to `application/json`.
|
|
214
|
+
*
|
|
215
|
+
* ### DAG-JSON
|
|
216
|
+
*
|
|
217
|
+
* [DAG-JSON](https://ipld.io/docs/codecs/known/dag-json/) expands on the `JSON` codec, adding the ability to contain [CID](https://docs.ipfs.tech/concepts/content-addressing/)s which act as links to other blocks, and byte arrays.
|
|
218
|
+
*
|
|
219
|
+
* `CID`s and byte arrays are represented using special object structures with a single `"/"` property.
|
|
220
|
+
*
|
|
221
|
+
* Using `DAG-JSON` has two important caveats:
|
|
222
|
+
*
|
|
223
|
+
* 1. Your `JSON` structure cannot contain an object with only a `"/"` property, as it will be interpreted as a special type.
|
|
224
|
+
* 2. Since `JSON` has no technical limit on number sizes, `DAG-JSON` also allows numbers larger than `Number.MAX_SAFE_INTEGER`. JavaScript requires use of `BigInt`s to represent numbers larger than this, and `JSON.parse` does not support them, so precision will be lost.
|
|
225
|
+
*
|
|
226
|
+
* Otherwise this codec follows the same rules as the `JSON` codec.
|
|
227
|
+
*
|
|
228
|
+
* ##### Using the DAG-JSON codec
|
|
229
|
+
*
|
|
230
|
+
* ```typescript
|
|
231
|
+
* import * as dagJson from '@ipld/dag-json'
|
|
232
|
+
*
|
|
233
|
+
* const block = new TextEncoder().encode(`{
|
|
234
|
+
* "hello": "world",
|
|
235
|
+
* "cid": {
|
|
236
|
+
* "/": "baeaaac3imvwgy3zao5xxe3de"
|
|
237
|
+
* },
|
|
238
|
+
* "buf": {
|
|
239
|
+
* "/": {
|
|
240
|
+
* "bytes": "AAECAwQ"
|
|
241
|
+
* }
|
|
242
|
+
* }
|
|
243
|
+
* }`)
|
|
244
|
+
*
|
|
245
|
+
* const obj = dagJson.decode(block)
|
|
246
|
+
*
|
|
247
|
+
* console.info(obj)
|
|
248
|
+
* // {
|
|
249
|
+
* // hello: 'world',
|
|
250
|
+
* // cid: CID(baeaaac3imvwgy3zao5xxe3de),
|
|
251
|
+
* // buf: Uint8Array(5) [ 0, 1, 2, 3, 4 ]
|
|
252
|
+
* // }
|
|
253
|
+
* ```
|
|
254
|
+
*
|
|
255
|
+
* ##### Content-Type
|
|
256
|
+
*
|
|
257
|
+
* When the `DAG-JSON` codec is encountered in the requested CID, the `Content-Type` header of the response will be set to `application/json`.
|
|
258
|
+
*
|
|
259
|
+
* `DAG-JSON` data can be parsed from the response by using the `.json()` function, which will return `CID`s/byte arrays as plain `{ "/": ... }` objects:
|
|
260
|
+
*
|
|
261
|
+
* ```typescript
|
|
262
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
263
|
+
* import * as dagJson from '@ipld/dag-json'
|
|
264
|
+
*
|
|
265
|
+
* const res = await verifiedFetch('ipfs://bafyDAGJSON')
|
|
266
|
+
*
|
|
267
|
+
* // either:
|
|
268
|
+
* const obj = await res.json()
|
|
269
|
+
* console.info(obj.cid) // { "/": "baeaaac3imvwgy3zao5xxe3de" }
|
|
270
|
+
* console.info(obj.buf) // { "/": { "bytes": "AAECAwQ" } }
|
|
271
|
+
* ```
|
|
272
|
+
*
|
|
273
|
+
* Alternatively, it can be decoded using the `@ipld/dag-json` module and the `.arrayBuffer()` method, in which case you will get `CID` objects and `Uint8Array`s:
|
|
274
|
+
*
|
|
275
|
+
*```typescript
|
|
276
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
277
|
+
* import * as dagJson from '@ipld/dag-json'
|
|
278
|
+
*
|
|
279
|
+
* const res = await verifiedFetch('ipfs://bafyDAGJSON')
|
|
280
|
+
*
|
|
281
|
+
* // or:
|
|
282
|
+
* const obj = dagJson.decode(await res.arrayBuffer())
|
|
283
|
+
* console.info(obj.cid) // CID(baeaaac3imvwgy3zao5xxe3de)
|
|
284
|
+
* console.info(obj.buf) // Uint8Array(5) [ 0, 1, 2, 3, 4 ]
|
|
285
|
+
* ```
|
|
286
|
+
*
|
|
287
|
+
* #### DAG-CBOR
|
|
288
|
+
*
|
|
289
|
+
* [DAG-CBOR](https://ipld.io/docs/codecs/known/dag-cbor/) uses the [Concise Binary Object Representation](https://cbor.io/) format for serialization instead of JSON.
|
|
290
|
+
*
|
|
291
|
+
* This supports more datatypes in a safer way than JSON and is smaller on the wire to boot so is usually preferable to JSON or DAG-JSON.
|
|
292
|
+
*
|
|
293
|
+
* ##### Content-Type
|
|
294
|
+
*
|
|
295
|
+
* Not all data types supported by `DAG-CBOR` can be successfully turned into JSON and back into the same binary form.
|
|
296
|
+
*
|
|
297
|
+
* When a decoded block can be round-tripped to JSON, the `Content-Type` will be set to `application/json`. In this case the `.json()` method on the `Response` object can be used to obtain an object representation of the response.
|
|
298
|
+
*
|
|
299
|
+
* When it cannot, the `Content-Type` will be `application/octet-stream` - in this case the `@ipld/dag-json` module must be used to deserialize the return value from `.arrayBuffer()`.
|
|
300
|
+
*
|
|
301
|
+
* ##### Detecting JSON-safe DAG-CBOR
|
|
302
|
+
*
|
|
303
|
+
* If the `Content-Type` header of the response is `application/json`, the `.json()` method may be used to access the response body in object form, otherwise the `.arrayBuffer()` method must be used to decode the raw bytes using the `@ipld/dag-cbor` module.
|
|
304
|
+
*
|
|
305
|
+
* ```typescript
|
|
306
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
307
|
+
* import * as dagCbor from '@ipld/dag-cbor'
|
|
308
|
+
*
|
|
309
|
+
* const res = await verifiedFetch('ipfs://bafyDagCborCID')
|
|
310
|
+
* let obj
|
|
311
|
+
*
|
|
312
|
+
* if (res.headers.get('Content-Type') === 'application/json') {
|
|
313
|
+
* // DAG-CBOR data can be safely decoded as JSON
|
|
314
|
+
* obj = await res.json()
|
|
315
|
+
* } else {
|
|
316
|
+
* // response contains non-JSON friendly data types
|
|
317
|
+
* obj = dagCbor.decode(await res.arrayBuffer())
|
|
318
|
+
* }
|
|
319
|
+
*
|
|
320
|
+
* console.info(obj) // ...
|
|
321
|
+
* ```
|
|
322
|
+
*
|
|
323
|
+
* ## The `Accept` header
|
|
324
|
+
*
|
|
325
|
+
* 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.
|
|
326
|
+
*
|
|
327
|
+
* 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 Acceptable](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/406) response will be returned:
|
|
328
|
+
*
|
|
329
|
+
* ```typescript
|
|
330
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
331
|
+
*
|
|
332
|
+
* const res = await verifiedFetch('ipfs://bafyJPEGImageCID', {
|
|
333
|
+
* headers: {
|
|
334
|
+
* accept: 'image/png'
|
|
335
|
+
* }
|
|
336
|
+
* })
|
|
337
|
+
*
|
|
338
|
+
* console.info(res.status) // 406 - the image was a JPEG but we specified PNG as the accept header
|
|
339
|
+
* ```
|
|
340
|
+
*
|
|
341
|
+
* It can also be used to skip processing the data from some formats such as `DAG-CBOR` if you wish to handle decoding it yourself:
|
|
342
|
+
*
|
|
343
|
+
* ```typescript
|
|
344
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
345
|
+
*
|
|
346
|
+
* const res = await verifiedFetch('ipfs://bafyDAGCBORCID', {
|
|
347
|
+
* headers: {
|
|
348
|
+
* accept: 'application/octet-stream'
|
|
349
|
+
* }
|
|
350
|
+
* })
|
|
351
|
+
*
|
|
352
|
+
* console.info(res.headers.get('accept')) // application/octet-stream
|
|
353
|
+
* const buf = await res.arrayBuffer() // raw bytes, not processed as JSON
|
|
354
|
+
* ```
|
|
355
|
+
*
|
|
141
356
|
* ## Comparison to fetch
|
|
142
357
|
*
|
|
143
358
|
* This module attempts to act as similarly to the `fetch()` API as possible.
|
|
@@ -155,7 +370,7 @@
|
|
|
155
370
|
* 2. IPNS protocol: `ipns://<peerId>` & `ipns://<publicKey>` & `ipns://<hostUri_Supporting_DnsLink_TxtRecords>`
|
|
156
371
|
* 3. CID instances: An actual CID instance `CID.parse('bafy...')`
|
|
157
372
|
*
|
|
158
|
-
* As well as support for pathing & params for
|
|
373
|
+
* As well as support for pathing & params for items 1 & 2 above according to [IPFS - Path Gateway Specification](https://specs.ipfs.tech/http-gateways/path-gateway) & [IPFS - Trustless Gateway Specification](https://specs.ipfs.tech/http-gateways/trustless-gateway/). Further refinement of those specifications specifically for web-based scenarios can be found in the [Web Pathing Specification IPIP](https://github.com/ipfs/specs/pull/453).
|
|
159
374
|
*
|
|
160
375
|
* If you pass a CID instance, it assumes you want the content for that specific CID only, and does not support pathing or params for that CID.
|
|
161
376
|
*
|
|
@@ -260,6 +475,9 @@ import type { ProgressEvent, ProgressOptions } from 'progress-events';
|
|
|
260
475
|
* The types for the first argument of the `verifiedFetch` function.
|
|
261
476
|
*/
|
|
262
477
|
export type Resource = string | CID;
|
|
478
|
+
export interface ResourceDetail {
|
|
479
|
+
resource: Resource;
|
|
480
|
+
}
|
|
263
481
|
export interface CIDDetail {
|
|
264
482
|
cid: CID;
|
|
265
483
|
path: string;
|
package/dist/src/index.d.ts.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmdG;AAMH,OAAO,KAAK,EAAE,KAAK,EAAE,MAAM,kBAAkB,CAAA;AAC7C,OAAO,KAAK,EAAE,iBAAiB,EAAE,4BAA4B,EAAE,qBAAqB,EAAE,MAAM,aAAa,CAAA;AACzG,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,eAAe,CAAA;AAC9C,OAAO,KAAK,EAAE,GAAG,EAAE,MAAM,kBAAkB,CAAA;AAC3C,OAAO,KAAK,EAAE,aAAa,EAAE,eAAe,EAAE,MAAM,iBAAiB,CAAA;AAErE;;GAEG;AACH,MAAM,MAAM,QAAQ,GAAG,MAAM,GAAG,GAAG,CAAA;AAEnC,MAAM,WAAW,cAAc;IAC7B,QAAQ,EAAE,QAAQ,CAAA;CACnB;AAED,MAAM,WAAW,SAAS;IACxB,GAAG,EAAE,GAAG,CAAA;IACR,IAAI,EAAE,MAAM,CAAA;CACb;AAED,MAAM,WAAW,cAAe,SAAQ,SAAS;IAC/C,KAAK,EAAE,KAAK,CAAA;CACb;AAED,MAAM,WAAW,aAAa;IAC5B,CAAC,QAAQ,EAAE,QAAQ,EAAE,OAAO,CAAC,EAAE,iBAAiB,GAAG,OAAO,CAAC,QAAQ,CAAC,CAAA;IACpE,KAAK,IAAI,OAAO,CAAC,IAAI,CAAC,CAAA;IACtB,IAAI,IAAI,OAAO,CAAC,IAAI,CAAC,CAAA;CACtB;AAED;;;GAGG;AACH,MAAM,WAAW,uBAAuB;IACtC,QAAQ,EAAE,MAAM,EAAE,CAAA;IAClB,OAAO,CAAC,EAAE,MAAM,EAAE,CAAA;CACnB;AAED,MAAM,WAAW,0BAA0B;IACzC;;;;;OAKG;IACH,iBAAiB,CAAC,EAAE,iBAAiB,CAAA;CACtC;AAED;;;;;GAKG;AACH,MAAM,WAAW,iBAAiB;IAChC;;;OAGG;IACH,CAAC,KAAK,EAAE,UAAU,EAAE,QAAQ,CAAC,EAAE,MAAM,GAAG,OAAO,CAAC,MAAM,GAAG,SAAS,CAAC,GAAG,MAAM,GAAG,SAAS,CAAA;CACzF;AAED,MAAM,MAAM,qBAAqB,GAE/B,SAAS,GAET,qBAAqB,GAAG,4BAA4B,GAAG,iBAAiB,CAAA;AAE1E,MAAM,MAAM,2BAA2B,GACrC,aAAa,CAAC,8BAA8B,EAAE,SAAS,CAAC,GACxD,aAAa,CAAC,6BAA6B,EAAE,MAAM,CAAC,GACpD,aAAa,CAAC,uCAAuC,EAAE,SAAS,CAAC,GACjE,aAAa,CAAC,4BAA4B,EAAE,SAAS,CAAC,GACtD,aAAa,CAAC,8BAA8B,EAAE,cAAc,CAAC,CAAA;AAE/D;;;;;;GAMG;AACH,MAAM,WAAW,iBAAkB,SAAQ,WAAW,EAAE,eAAe,CAAC,qBAAqB,GAAG,2BAA2B,CAAC;CAC3H;AAED;;GAEG;AACH,wBAAsB,mBAAmB,CAAE,IAAI,CAAC,EAAE,KAAK,GAAG,uBAAuB,EAAE,OAAO,CAAC,EAAE,0BAA0B,GAAG,OAAO,CAAC,aAAa,CAAC,CAsB/I;AAED,OAAO,EAAE,aAAa,EAAE,MAAM,gBAAgB,CAAA"}
|
package/dist/src/index.js
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
*
|
|
4
4
|
* `@helia/verified-fetch` provides a [fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)-like API for retrieving content from the [IPFS](https://ipfs.tech/) network.
|
|
5
5
|
*
|
|
6
|
-
* All content is retrieved in a [trustless manner](https://www.techopedia.com/definition/trustless), and the integrity of all bytes are verified by comparing hashes of the data.
|
|
6
|
+
* All content is retrieved in a [trustless manner](https://www.techopedia.com/definition/trustless), and the integrity of all bytes are verified by comparing hashes of the data. By default, CIDs are retrieved over HTTP from [trustless gateways](https://specs.ipfs.tech/http-gateways/trustless-gateway/).
|
|
7
7
|
*
|
|
8
8
|
* This is a marked improvement over `fetch` which offers no such protections and is vulnerable to all sorts of attacks like [Content Spoofing](https://owasp.org/www-community/attacks/Content_Spoofing), [DNS Hijacking](https://en.wikipedia.org/wiki/DNS_hijacking), etc.
|
|
9
9
|
*
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
34
34
|
* import { CID } from 'multiformats/cid'
|
|
35
35
|
*
|
|
36
|
-
* const cid = CID.parse('bafyFoo') // some
|
|
36
|
+
* const cid = CID.parse('bafyFoo') // some json file
|
|
37
37
|
* const response = await verifiedFetch(cid)
|
|
38
38
|
* const json = await response.json()
|
|
39
39
|
* ```
|
|
@@ -114,7 +114,7 @@
|
|
|
114
114
|
*
|
|
115
115
|
* ### Custom content-type parsing
|
|
116
116
|
*
|
|
117
|
-
* By default, `@helia/verified-fetch` sets the `Content-Type` header as `application/octet-stream` - this is because the `.json()`, `.text()`, `.blob()`, and `.arrayBuffer()` methods will usually work as expected without a detailed content type.
|
|
117
|
+
* By default, if the response can be parsed as JSON, `@helia/verified-fetch` sets the `Content-Type` header as `application/json`, otherwise it sets it as `application/octet-stream` - this is because the `.json()`, `.text()`, `.blob()`, and `.arrayBuffer()` methods will usually work as expected without a detailed content type.
|
|
118
118
|
*
|
|
119
119
|
* If you require an accurate content-type you can provide a `contentTypeParser` function as an option to `createVerifiedFetch` to handle parsing the content type.
|
|
120
120
|
*
|
|
@@ -138,6 +138,221 @@
|
|
|
138
138
|
* })
|
|
139
139
|
* ```
|
|
140
140
|
*
|
|
141
|
+
* ### IPLD codec handling
|
|
142
|
+
*
|
|
143
|
+
* IPFS supports several data formats (typically referred to as codecs) which are included in the CID. `@helia/verified-fetch` attempts to abstract away some of the details for easier consumption.
|
|
144
|
+
*
|
|
145
|
+
* #### DAG-PB
|
|
146
|
+
*
|
|
147
|
+
* [DAG-PB](https://ipld.io/docs/codecs/known/dag-pb/) is the codec we are most likely to encounter, it is what [UnixFS](https://github.com/ipfs/specs/blob/main/UNIXFS.md) uses under the hood.
|
|
148
|
+
*
|
|
149
|
+
* ##### Using the DAG-PB codec as a Blob
|
|
150
|
+
*
|
|
151
|
+
* ```typescript
|
|
152
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
153
|
+
*
|
|
154
|
+
* const res = await verifiedFetch('ipfs://Qmfoo')
|
|
155
|
+
* const blob = await res.blob()
|
|
156
|
+
*
|
|
157
|
+
* console.info(blob) // Blob { size: x, type: 'application/octet-stream' }
|
|
158
|
+
* ```
|
|
159
|
+
*
|
|
160
|
+
* ##### Using the DAG-PB codec as an ArrayBuffer
|
|
161
|
+
*
|
|
162
|
+
* ```typescript
|
|
163
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
164
|
+
*
|
|
165
|
+
* const res = await verifiedFetch('ipfs://Qmfoo')
|
|
166
|
+
* const buf = await res.arrayBuffer()
|
|
167
|
+
*
|
|
168
|
+
* console.info(buf) // ArrayBuffer { [Uint8Contents]: < ... >, byteLength: x }
|
|
169
|
+
* ```
|
|
170
|
+
*
|
|
171
|
+
* ##### Using the DAG-PB codec as a stream
|
|
172
|
+
*
|
|
173
|
+
* ```typescript
|
|
174
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
175
|
+
*
|
|
176
|
+
* const res = await verifiedFetch('ipfs://Qmfoo')
|
|
177
|
+
* const reader = res.body?.getReader()
|
|
178
|
+
*
|
|
179
|
+
* while (true) {
|
|
180
|
+
* const next = await reader.read()
|
|
181
|
+
*
|
|
182
|
+
* if (next?.done === true) {
|
|
183
|
+
* break
|
|
184
|
+
* }
|
|
185
|
+
*
|
|
186
|
+
* if (next?.value != null) {
|
|
187
|
+
* console.info(next.value) // Uint8Array(x) [ ... ]
|
|
188
|
+
* }
|
|
189
|
+
* }
|
|
190
|
+
* ```
|
|
191
|
+
*
|
|
192
|
+
* ##### Content-Type
|
|
193
|
+
*
|
|
194
|
+
* When fetching `DAG-PB` data, the content type will be set to `application/octet-stream` unless a custom content-type parser is configured.
|
|
195
|
+
*
|
|
196
|
+
* #### JSON
|
|
197
|
+
*
|
|
198
|
+
* The JSON codec is a very simple codec, a block parseable with this codec is a JSON string encoded into a `Uint8Array`.
|
|
199
|
+
*
|
|
200
|
+
* ##### Using the JSON codec
|
|
201
|
+
*
|
|
202
|
+
* ```typescript
|
|
203
|
+
* import * as json from 'multiformats/codecs/json'
|
|
204
|
+
*
|
|
205
|
+
* const block = new TextEncoder().encode('{ "hello": "world" }')
|
|
206
|
+
* const obj = json.decode(block)
|
|
207
|
+
*
|
|
208
|
+
* console.info(obj) // { hello: 'world' }
|
|
209
|
+
* ```
|
|
210
|
+
*
|
|
211
|
+
* ##### Content-Type
|
|
212
|
+
*
|
|
213
|
+
* When the `JSON` codec is encountered, the `Content-Type` header of the response will be set to `application/json`.
|
|
214
|
+
*
|
|
215
|
+
* ### DAG-JSON
|
|
216
|
+
*
|
|
217
|
+
* [DAG-JSON](https://ipld.io/docs/codecs/known/dag-json/) expands on the `JSON` codec, adding the ability to contain [CID](https://docs.ipfs.tech/concepts/content-addressing/)s which act as links to other blocks, and byte arrays.
|
|
218
|
+
*
|
|
219
|
+
* `CID`s and byte arrays are represented using special object structures with a single `"/"` property.
|
|
220
|
+
*
|
|
221
|
+
* Using `DAG-JSON` has two important caveats:
|
|
222
|
+
*
|
|
223
|
+
* 1. Your `JSON` structure cannot contain an object with only a `"/"` property, as it will be interpreted as a special type.
|
|
224
|
+
* 2. Since `JSON` has no technical limit on number sizes, `DAG-JSON` also allows numbers larger than `Number.MAX_SAFE_INTEGER`. JavaScript requires use of `BigInt`s to represent numbers larger than this, and `JSON.parse` does not support them, so precision will be lost.
|
|
225
|
+
*
|
|
226
|
+
* Otherwise this codec follows the same rules as the `JSON` codec.
|
|
227
|
+
*
|
|
228
|
+
* ##### Using the DAG-JSON codec
|
|
229
|
+
*
|
|
230
|
+
* ```typescript
|
|
231
|
+
* import * as dagJson from '@ipld/dag-json'
|
|
232
|
+
*
|
|
233
|
+
* const block = new TextEncoder().encode(`{
|
|
234
|
+
* "hello": "world",
|
|
235
|
+
* "cid": {
|
|
236
|
+
* "/": "baeaaac3imvwgy3zao5xxe3de"
|
|
237
|
+
* },
|
|
238
|
+
* "buf": {
|
|
239
|
+
* "/": {
|
|
240
|
+
* "bytes": "AAECAwQ"
|
|
241
|
+
* }
|
|
242
|
+
* }
|
|
243
|
+
* }`)
|
|
244
|
+
*
|
|
245
|
+
* const obj = dagJson.decode(block)
|
|
246
|
+
*
|
|
247
|
+
* console.info(obj)
|
|
248
|
+
* // {
|
|
249
|
+
* // hello: 'world',
|
|
250
|
+
* // cid: CID(baeaaac3imvwgy3zao5xxe3de),
|
|
251
|
+
* // buf: Uint8Array(5) [ 0, 1, 2, 3, 4 ]
|
|
252
|
+
* // }
|
|
253
|
+
* ```
|
|
254
|
+
*
|
|
255
|
+
* ##### Content-Type
|
|
256
|
+
*
|
|
257
|
+
* When the `DAG-JSON` codec is encountered in the requested CID, the `Content-Type` header of the response will be set to `application/json`.
|
|
258
|
+
*
|
|
259
|
+
* `DAG-JSON` data can be parsed from the response by using the `.json()` function, which will return `CID`s/byte arrays as plain `{ "/": ... }` objects:
|
|
260
|
+
*
|
|
261
|
+
* ```typescript
|
|
262
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
263
|
+
* import * as dagJson from '@ipld/dag-json'
|
|
264
|
+
*
|
|
265
|
+
* const res = await verifiedFetch('ipfs://bafyDAGJSON')
|
|
266
|
+
*
|
|
267
|
+
* // either:
|
|
268
|
+
* const obj = await res.json()
|
|
269
|
+
* console.info(obj.cid) // { "/": "baeaaac3imvwgy3zao5xxe3de" }
|
|
270
|
+
* console.info(obj.buf) // { "/": { "bytes": "AAECAwQ" } }
|
|
271
|
+
* ```
|
|
272
|
+
*
|
|
273
|
+
* Alternatively, it can be decoded using the `@ipld/dag-json` module and the `.arrayBuffer()` method, in which case you will get `CID` objects and `Uint8Array`s:
|
|
274
|
+
*
|
|
275
|
+
*```typescript
|
|
276
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
277
|
+
* import * as dagJson from '@ipld/dag-json'
|
|
278
|
+
*
|
|
279
|
+
* const res = await verifiedFetch('ipfs://bafyDAGJSON')
|
|
280
|
+
*
|
|
281
|
+
* // or:
|
|
282
|
+
* const obj = dagJson.decode(await res.arrayBuffer())
|
|
283
|
+
* console.info(obj.cid) // CID(baeaaac3imvwgy3zao5xxe3de)
|
|
284
|
+
* console.info(obj.buf) // Uint8Array(5) [ 0, 1, 2, 3, 4 ]
|
|
285
|
+
* ```
|
|
286
|
+
*
|
|
287
|
+
* #### DAG-CBOR
|
|
288
|
+
*
|
|
289
|
+
* [DAG-CBOR](https://ipld.io/docs/codecs/known/dag-cbor/) uses the [Concise Binary Object Representation](https://cbor.io/) format for serialization instead of JSON.
|
|
290
|
+
*
|
|
291
|
+
* This supports more datatypes in a safer way than JSON and is smaller on the wire to boot so is usually preferable to JSON or DAG-JSON.
|
|
292
|
+
*
|
|
293
|
+
* ##### Content-Type
|
|
294
|
+
*
|
|
295
|
+
* Not all data types supported by `DAG-CBOR` can be successfully turned into JSON and back into the same binary form.
|
|
296
|
+
*
|
|
297
|
+
* When a decoded block can be round-tripped to JSON, the `Content-Type` will be set to `application/json`. In this case the `.json()` method on the `Response` object can be used to obtain an object representation of the response.
|
|
298
|
+
*
|
|
299
|
+
* When it cannot, the `Content-Type` will be `application/octet-stream` - in this case the `@ipld/dag-json` module must be used to deserialize the return value from `.arrayBuffer()`.
|
|
300
|
+
*
|
|
301
|
+
* ##### Detecting JSON-safe DAG-CBOR
|
|
302
|
+
*
|
|
303
|
+
* If the `Content-Type` header of the response is `application/json`, the `.json()` method may be used to access the response body in object form, otherwise the `.arrayBuffer()` method must be used to decode the raw bytes using the `@ipld/dag-cbor` module.
|
|
304
|
+
*
|
|
305
|
+
* ```typescript
|
|
306
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
307
|
+
* import * as dagCbor from '@ipld/dag-cbor'
|
|
308
|
+
*
|
|
309
|
+
* const res = await verifiedFetch('ipfs://bafyDagCborCID')
|
|
310
|
+
* let obj
|
|
311
|
+
*
|
|
312
|
+
* if (res.headers.get('Content-Type') === 'application/json') {
|
|
313
|
+
* // DAG-CBOR data can be safely decoded as JSON
|
|
314
|
+
* obj = await res.json()
|
|
315
|
+
* } else {
|
|
316
|
+
* // response contains non-JSON friendly data types
|
|
317
|
+
* obj = dagCbor.decode(await res.arrayBuffer())
|
|
318
|
+
* }
|
|
319
|
+
*
|
|
320
|
+
* console.info(obj) // ...
|
|
321
|
+
* ```
|
|
322
|
+
*
|
|
323
|
+
* ## The `Accept` header
|
|
324
|
+
*
|
|
325
|
+
* 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.
|
|
326
|
+
*
|
|
327
|
+
* 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 Acceptable](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/406) response will be returned:
|
|
328
|
+
*
|
|
329
|
+
* ```typescript
|
|
330
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
331
|
+
*
|
|
332
|
+
* const res = await verifiedFetch('ipfs://bafyJPEGImageCID', {
|
|
333
|
+
* headers: {
|
|
334
|
+
* accept: 'image/png'
|
|
335
|
+
* }
|
|
336
|
+
* })
|
|
337
|
+
*
|
|
338
|
+
* console.info(res.status) // 406 - the image was a JPEG but we specified PNG as the accept header
|
|
339
|
+
* ```
|
|
340
|
+
*
|
|
341
|
+
* It can also be used to skip processing the data from some formats such as `DAG-CBOR` if you wish to handle decoding it yourself:
|
|
342
|
+
*
|
|
343
|
+
* ```typescript
|
|
344
|
+
* import { verifiedFetch } from '@helia/verified-fetch'
|
|
345
|
+
*
|
|
346
|
+
* const res = await verifiedFetch('ipfs://bafyDAGCBORCID', {
|
|
347
|
+
* headers: {
|
|
348
|
+
* accept: 'application/octet-stream'
|
|
349
|
+
* }
|
|
350
|
+
* })
|
|
351
|
+
*
|
|
352
|
+
* console.info(res.headers.get('accept')) // application/octet-stream
|
|
353
|
+
* const buf = await res.arrayBuffer() // raw bytes, not processed as JSON
|
|
354
|
+
* ```
|
|
355
|
+
*
|
|
141
356
|
* ## Comparison to fetch
|
|
142
357
|
*
|
|
143
358
|
* This module attempts to act as similarly to the `fetch()` API as possible.
|
|
@@ -155,7 +370,7 @@
|
|
|
155
370
|
* 2. IPNS protocol: `ipns://<peerId>` & `ipns://<publicKey>` & `ipns://<hostUri_Supporting_DnsLink_TxtRecords>`
|
|
156
371
|
* 3. CID instances: An actual CID instance `CID.parse('bafy...')`
|
|
157
372
|
*
|
|
158
|
-
* As well as support for pathing & params for
|
|
373
|
+
* As well as support for pathing & params for items 1 & 2 above according to [IPFS - Path Gateway Specification](https://specs.ipfs.tech/http-gateways/path-gateway) & [IPFS - Trustless Gateway Specification](https://specs.ipfs.tech/http-gateways/trustless-gateway/). Further refinement of those specifications specifically for web-based scenarios can be found in the [Web Pathing Specification IPIP](https://github.com/ipfs/specs/pull/453).
|
|
159
374
|
*
|
|
160
375
|
* If you pass a CID instance, it assumes you want the content for that specific CID only, and does not support pathing or params for that CID.
|
|
161
376
|
*
|
package/dist/src/index.js.map
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAmdG;AAEH,OAAO,EAAE,gBAAgB,EAAE,MAAM,sBAAsB,CAAA;AACvD,OAAO,EAAE,eAAe,EAAE,MAAM,aAAa,CAAA;AAC7C,OAAO,EAAE,oBAAoB,EAAE,MAAM,gBAAgB,CAAA;AACrD,OAAO,EAAE,aAAa,IAAI,kBAAkB,EAAE,MAAM,qBAAqB,CAAA;AAuFzE;;GAEG;AACH,MAAM,CAAC,KAAK,UAAU,mBAAmB,CAAE,IAAsC,EAAE,OAAoC;IACrH,MAAM,iBAAiB,GAAkC,OAAO,EAAE,iBAAiB,CAAA;IAEnF,IAAI,CAAC,OAAO,CAAC,IAAI,CAAC,EAAE,CAAC;QACnB,IAAI,GAAG,MAAM,eAAe,CAAC;YAC3B,YAAY,EAAE;gBACZ,gBAAgB,CAAC;oBACf,QAAQ,EAAE,IAAI,EAAE,QAAQ;iBACzB,CAAC;aACH;YACD,OAAO,EAAE,CAAC,IAAI,EAAE,OAAO,IAAI,CAAC,4BAA4B,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,oBAAoB,CAAC,SAAS,CAAC,CAAC;SAC/G,CAAC,CAAA;IACJ,CAAC;IAED,MAAM,qBAAqB,GAAG,IAAI,kBAAkB,CAAC,EAAE,KAAK,EAAE,IAAI,EAAE,EAAE,EAAE,iBAAiB,EAAE,CAAC,CAAA;IAC5F,KAAK,UAAU,aAAa,CAAE,QAAkB,EAAE,OAA2B;QAC3E,OAAO,qBAAqB,CAAC,KAAK,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAA;IACvD,CAAC;IACD,aAAa,CAAC,IAAI,GAAG,qBAAqB,CAAC,IAAI,CAAC,IAAI,CAAC,qBAAqB,CAAC,CAAA;IAC3E,aAAa,CAAC,KAAK,GAAG,qBAAqB,CAAC,KAAK,CAAC,IAAI,CAAC,qBAAqB,CAAC,CAAA;IAE7E,OAAO,aAAa,CAAA;AACtB,CAAC;AAED,OAAO,EAAE,aAAa,EAAE,MAAM,gBAAgB,CAAA;AAE9C,SAAS,OAAO,CAAE,GAAQ;IACxB,0EAA0E;IAC1E,OAAO,GAAG,EAAE,UAAU,IAAI,IAAI;QAC5B,GAAG,EAAE,SAAS,IAAI,IAAI;QACtB,GAAG,EAAE,EAAE,IAAI,IAAI;QACf,GAAG,EAAE,IAAI,IAAI,IAAI;QACjB,GAAG,EAAE,KAAK,IAAI,IAAI,CAAA;AACtB,CAAC"}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"types.d.ts","sourceRoot":"","sources":["../../src/types.ts"],"names":[],"mappings":"AAAA,MAAM,MAAM,sBAAsB,GAAG,KAAK,GAAG,KAAK,GAAG,KAAK,GAAG,aAAa,GAAG,UAAU,GAAG,UAAU,GAAG,MAAM,GAAG,MAAM,CAAA"}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"types.js","sourceRoot":"","sources":["../../src/types.ts"],"names":[],"mappings":""}
|
|
@@ -0,0 +1,7 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Take a `DAG-CBOR` encoded `Uint8Array`, deserialize it as an object and
|
|
3
|
+
* re-serialize it in a form that can be passed to `JSON.serialize` and then
|
|
4
|
+
* `JSON.parse` without losing any data.
|
|
5
|
+
*/
|
|
6
|
+
export declare function dagCborToSafeJSON(buf: Uint8Array): string;
|
|
7
|
+
//# sourceMappingURL=dag-cbor-to-safe-json.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"dag-cbor-to-safe-json.d.ts","sourceRoot":"","sources":["../../../src/utils/dag-cbor-to-safe-json.ts"],"names":[],"mappings":"AAgBA;;;;GAIG;AACH,wBAAgB,iBAAiB,CAAE,GAAG,EAAE,UAAU,GAAG,MAAM,CAsB1D"}
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
import { decode } from 'cborg';
|
|
2
|
+
import { encode } from 'cborg/json';
|
|
3
|
+
import { CID } from 'multiformats/cid';
|
|
4
|
+
// https://github.com/ipfs/go-ipfs/issues/3570#issuecomment-273931692
|
|
5
|
+
const CID_CBOR_TAG = 0x2A;
|
|
6
|
+
function cidDecoder(bytes) {
|
|
7
|
+
if (bytes[0] !== 0) {
|
|
8
|
+
throw new Error('Invalid CID for CBOR tag 42; expected leading 0x00');
|
|
9
|
+
}
|
|
10
|
+
return CID.decode(bytes.subarray(1)); // ignore leading 0x00
|
|
11
|
+
}
|
|
12
|
+
/**
|
|
13
|
+
* Take a `DAG-CBOR` encoded `Uint8Array`, deserialize it as an object and
|
|
14
|
+
* re-serialize it in a form that can be passed to `JSON.serialize` and then
|
|
15
|
+
* `JSON.parse` without losing any data.
|
|
16
|
+
*/
|
|
17
|
+
export function dagCborToSafeJSON(buf) {
|
|
18
|
+
const tags = [];
|
|
19
|
+
tags[CID_CBOR_TAG] = cidDecoder;
|
|
20
|
+
const obj = decode(buf, {
|
|
21
|
+
allowIndefinite: false,
|
|
22
|
+
coerceUndefinedToNull: true,
|
|
23
|
+
allowNaN: false,
|
|
24
|
+
allowInfinity: false,
|
|
25
|
+
strict: true,
|
|
26
|
+
useMaps: false,
|
|
27
|
+
rejectDuplicateMapKeys: true,
|
|
28
|
+
tags,
|
|
29
|
+
// this is different to `DAG-CBOR` - the reason we disallow BigInts is
|
|
30
|
+
// because we are about to re-encode to `JSON` which does not support
|
|
31
|
+
// BigInts. Blocks containing large numbers should be deserialized using a
|
|
32
|
+
// cbor decoder instead
|
|
33
|
+
allowBigInt: false
|
|
34
|
+
});
|
|
35
|
+
return new TextDecoder().decode(encode(obj));
|
|
36
|
+
}
|
|
37
|
+
//# sourceMappingURL=dag-cbor-to-safe-json.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"dag-cbor-to-safe-json.js","sourceRoot":"","sources":["../../../src/utils/dag-cbor-to-safe-json.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,OAAO,CAAA;AAC9B,OAAO,EAAE,MAAM,EAAE,MAAM,YAAY,CAAA;AACnC,OAAO,EAAE,GAAG,EAAE,MAAM,kBAAkB,CAAA;AAGtC,qEAAqE;AACrE,MAAM,YAAY,GAAG,IAAI,CAAA;AAEzB,SAAS,UAAU,CAAE,KAAiB;IACpC,IAAI,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,EAAE,CAAC;QACnB,MAAM,IAAI,KAAK,CAAC,oDAAoD,CAAC,CAAA;IACvE,CAAC;IAED,OAAO,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,QAAQ,CAAC,CAAC,CAAC,CAAC,CAAA,CAAC,sBAAsB;AAC7D,CAAC;AAED;;;;GAIG;AACH,MAAM,UAAU,iBAAiB,CAAE,GAAe;IAChD,MAAM,IAAI,GAAiB,EAAE,CAAA;IAC7B,IAAI,CAAC,YAAY,CAAC,GAAG,UAAU,CAAA;IAE/B,MAAM,GAAG,GAAG,MAAM,CAAC,GAAG,EAAE;QACtB,eAAe,EAAE,KAAK;QACtB,qBAAqB,EAAE,IAAI;QAC3B,QAAQ,EAAE,KAAK;QACf,aAAa,EAAE,KAAK;QACpB,MAAM,EAAE,IAAI;QACZ,OAAO,EAAE,KAAK;QACd,sBAAsB,EAAE,IAAI;QAC5B,IAAI;QAEJ,sEAAsE;QACtE,qEAAqE;QACrE,0EAA0E;QAC1E,uBAAuB;QACvB,WAAW,EAAE,KAAK;KACnB,CAAC,CAAA;IAEF,OAAO,IAAI,WAAW,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAA;AAC9C,CAAC"}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"get-content-disposition-filename.d.ts","sourceRoot":"","sources":["../../../src/utils/get-content-disposition-filename.ts"],"names":[],"mappings":"AAAA;;;GAGG;AACH,wBAAgB,6BAA6B,CAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,CAQvE"}
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Takes a filename URL param and returns a string for use in a
|
|
3
|
+
* `Content-Disposition` header
|
|
4
|
+
*/
|
|
5
|
+
export function getContentDispositionFilename(filename) {
|
|
6
|
+
const asciiOnly = replaceNonAsciiCharacters(filename);
|
|
7
|
+
if (asciiOnly === filename) {
|
|
8
|
+
return `filename="${filename}"`;
|
|
9
|
+
}
|
|
10
|
+
return `filename="${asciiOnly}"; filename*=UTF-8''${encodeURIComponent(filename)}`;
|
|
11
|
+
}
|
|
12
|
+
function replaceNonAsciiCharacters(filename) {
|
|
13
|
+
// eslint-disable-next-line no-control-regex
|
|
14
|
+
return filename.replace(/[^\x00-\x7F]/g, '_');
|
|
15
|
+
}
|
|
16
|
+
//# sourceMappingURL=get-content-disposition-filename.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"get-content-disposition-filename.js","sourceRoot":"","sources":["../../../src/utils/get-content-disposition-filename.ts"],"names":[],"mappings":"AAAA;;;GAGG;AACH,MAAM,UAAU,6BAA6B,CAAE,QAAgB;IAC7D,MAAM,SAAS,GAAG,yBAAyB,CAAC,QAAQ,CAAC,CAAA;IAErD,IAAI,SAAS,KAAK,QAAQ,EAAE,CAAC;QAC3B,OAAO,aAAa,QAAQ,GAAG,CAAA;IACjC,CAAC;IAED,OAAO,aAAa,SAAS,uBAAuB,kBAAkB,CAAC,QAAQ,CAAC,EAAE,CAAA;AACpF,CAAC;AAED,SAAS,yBAAyB,CAAE,QAAgB;IAClD,4CAA4C;IAC5C,OAAO,QAAQ,CAAC,OAAO,CAAC,eAAe,EAAE,GAAG,CAAC,CAAA;AAC/C,CAAC"}
|