Tracking(aztec.js): browser errors

[rahul-kothari]

Aztec.JS seems to be hard to use on the browser due to various vite errors. Let's change that

Tasks

Preview Give feedback

1. @aztec/aztec.js imports testing stuff (and fs) #5050
   C-aztec.js from-community +2
2. building SSR with vite fails due to fs/promises #6073
   S-blocked +1
3. bug: vite build fails due to out of memory error #6527
   C-bb.js T-bug from-community +3
4. chore(ci): Create web bundle for aztec.js #3864
   A-devops S-needs-discussion +2
5. Remove top-level await from aztec.js #9959
   from-community +1
6. Make aztec.js more browser friendly #9248
   from-community +1
7. chore: remove top level await on bb.js #10184
   +0
8. feat: Create a vite box #10114
   +0
   
9. Add Buffer imports to files that use it #10477
   T-feature-request +1

[olehmisar]

@rahul-kothari please track #9959 and #9248

[olehmisar]

EDIT: the info below is not accurate. It works fine unless I am using some aztec.js contract stuff. I guess the config below only works for bb.js and maybe foundation.

ORIGINAL COMMENT:

An update what is still required as of 0.66.0 to make aztec.js work in browser

In main.ts:

import { Buffer } from 'buffer'

globalThis.Buffer ??= Buffer
// @ts-expect-error
globalThis.process ??= { env: {} }

In vite.config.ts:

export default defineConfig({
  plugins: [
    resolve({
      util: 'export const inspect = {}', // https://github.com/AztecProtocol/aztec-packages/issues/8881
    }),
  ],
  build: {
    target: "esnext",
  },
  optimizeDeps: {
    esbuildOptions: {
      target: "esnext",
    },
  },
});

[olehmisar]

@rahul-kothari track #10741 please

[rahul-kothari]

looks like 10741 is closed already @olehmisar ?