Update http-encoding to fix crashes due to wasm-brotli

We now use brotli-wasm instead, our own module which includes the
latest version of brotli, and workarounds for webpack compilation
issues that otherwise break all sorts of things.

Author: pimterry

automation/webpack.common.ts

@@ -118,7 +118,12 @@ export default <Webpack.Configuration>{
                     // issues? This helps protect against possible corruptions:
                     const manifest = originalManifest.map((entry: any) => {
                         const asset = compilation.getAsset(entry.url);
-                        entry.integrity = ssri.fromData(asset.source.source()).toString();
+                        const assetSource = asset.source.source();
+                        entry.integrity = ssri.fromData(
+                            assetSource instanceof ArrayBuffer
+                                ? Buffer.from(assetSource) // Wasm!
+                                : assetSource
+                        ).toString();
                         return entry;
                     });
 

custom-typings/wasm-brotli.d.ts

@@ -7,4 +7,9 @@
 [[headers]]
     for = "/*"
     [headers.values]
-        Content-Security-Policy = "frame-ancestors 'none'"
+        Content-Security-Policy = "frame-ancestors 'none'"
+
+[[headers]]
+    for = "/*.wasm"
+    [headers.values]
+        Content-Type = "application/wasm"

netlify.toml

@@ -81,7 +81,7 @@
     "dompurify": "^2.1.1",
     "graphql": "^14.7.0",
     "har-validator": "^5.1.3",
-    "http-encoding": "^1.0.1",
+    "http-encoding": "^1.1.0",
     "httpsnippet": "^1.25.0",
     "idb-keyval": "^3.2.0",
     "js-beautify": "^1.8.8",