fix: update readmes and bundle sizes

Author: achingbrain

packages/gateway-conformance/.aegir.js

@@ -5,6 +5,9 @@ const log = logger('aegir')
 
 /** @type {import('aegir').PartialOptions} */
 export default {
+  build: {
+    bundlesizeMax: '1KB'
+  },
   test: {
     files: ['./dist/src/*.spec.js'],
     before: async (options) => {

packages/gateway-conformance/README.md

@@ -30,7 +30,8 @@ repo and examine the changes made.
 
 -->
 
-Runs Gateway Conformance tests against @helia/verified-fetch using Kubo as a backing trustless-gateway.
+Runs Gateway Conformance tests against @helia/verified-fetch using Kubo as a
+backing trustless-gateway.
 
 ## Example - Testing a new @helia/verified-fetch release
 
@@ -67,15 +68,17 @@ $ node dist/src/demo-server.js # in terminal 1
 $ curl -v GET http://localhost:3442/ipfs/bafkqabtimvwgy3yk/  # in terminal 2
 ```
 
-# Troubleshooting
+## Troubleshooting
 
-## Missing file in gateway-conformance-fixtures folder
+### Missing file in gateway-conformance-fixtures folder
 
 If you see the following error:
 
-> ENOENT: no such file or directory, open '[...]/helia-verified-fetch/packages/gateway-conformance/dist/src/...
+> ENOENT: no such file or directory, open '\[...]/helia-verified-fetch/packages/gateway-conformance/dist/src/...
 
-This likely means the docker container is not executing properly for some reason. You can try running the following command to see if there are any errors: `DEBUG="-mocha*,*,*:trace" npm run test`
+This likely means the docker container is not executing properly for some
+reason. You can try running the following command to see if there are any
+errors: `DEBUG="-mocha*,*,*:trace" npm run test`
 
 # Install
 

packages/gateway-conformance/src/index.ts

@@ -1,7 +1,8 @@
 /**
  * @packageDocumentation
  *
- * Runs Gateway Conformance tests against @helia/verified-fetch using Kubo as a backing trustless-gateway.
+ * Runs Gateway Conformance tests against @helia/verified-fetch using Kubo as a
+ * backing trustless-gateway.
  *
  * @example Testing a new @helia/verified-fetch release
  *
@@ -38,14 +39,16 @@
  * $ curl -v GET http://localhost:3442/ipfs/bafkqabtimvwgy3yk/  # in terminal 2
  * ```
  *
- * # Troubleshooting
+ * ## Troubleshooting
  *
- * ## Missing file in gateway-conformance-fixtures folder
+ * ### Missing file in gateway-conformance-fixtures folder
  *
  * If you see the following error:
  * > ENOENT: no such file or directory, open '[...]/helia-verified-fetch/packages/gateway-conformance/dist/src/...
  *
- * This likely means the docker container is not executing properly for some reason. You can try running the following command to see if there are any errors: `DEBUG="-mocha*,*,*:trace" npm run test`
+ * This likely means the docker container is not executing properly for some
+ * reason. You can try running the following command to see if there are any
+ * errors: `DEBUG="-mocha*,*,*:trace" npm run test`
  */
 
 export {}

packages/interop/.aegir.js

@@ -7,6 +7,9 @@ const IPFS_PATH = resolve(tmpdir(), 'verified-fetch-interop-ipfs-repo')
 
 /** @type {import('aegir').PartialOptions} */
 export default {
+  build: {
+    bundlesizeMax: '1KB'
+  },
   dependencyCheck: {
     ignore: [
       '@helia/delegated-routing-v1-http-api-server',

packages/verified-fetch/.aegir.js

@@ -1,7 +1,7 @@
 /** @type {import('aegir').PartialOptions} */
 const options = {
   build: {
-    bundlesizeMax: '132KB'
+    bundlesizeMax: '355KB'
   }
 }
 

packages/verified-fetch/README.md

@@ -306,7 +306,7 @@ When fetching `DAG-PB` data, the content type will be set to `application/octet-
 
 #### JSON
 
-The JSON codec is a very simple codec, a block decodable with this codec is a JSON string encoded into a `Uint8Array`.
+The JSON codec is a very simple codec, a block parseable with this codec is a JSON string encoded into a `Uint8Array`.
 
 ##### Using the JSON codec
 
@@ -554,7 +554,7 @@ This library supports the following methods of fetching web3 content from IPFS:
 2. IPNS protocol: `ipns://<peerId>` & `ipns://<publicKey>` & `ipns://<hostUri_Supporting_DnsLink_TxtRecords>`
 3. CID instances: An actual CID instance `CID.parse('bafy...')`
 
-As well as support for paths & 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).
+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).
 
 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.