chore: fix vite config to support firefox

[numtel]

Description

Problem*

Resolves #11

Summary*

This fixes the wasm loading on Firefox for me.

Additional Context

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[numtel]

That second commit fixes this error when running npm run build:

x Build failed in 7.86s
error during build:
[vite:esbuild-transpile] Transform failed with 1 error:
assets/index-!~{003}~.js:2143:25: ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)

But then there's still the error about not having @aztec/bb.js since it's marked as external. It's 62 MB? How is this expected to be loaded in production?

TypeError: Failed to resolve module specifier '@aztec/bb.js'

[numtel]

With this latest commit, it fixes yarn build as well as yarn dev.

To do a similar header configuration on Cloudflare, setup a rule like this:

[critesjosh]

Does this work for you? It's working for me on Brave, but I see this with yarn dev on Firefox.

It's working with yarn build and yarn preview on firefox.

[numtel]

Just checked again, working for me with yarn dev. That's the error that occurs with those 2 COEP/COOP headers in Firefox. Can you console.log(req.headers) (in the middleware function) and check what your user agent is?