task: delete vanilla js prototype\n\n- Removed vanilla/ directory and web/dist/vanilla directory\n- Updated Makefile, Dockerfile, and CI workflow to remove vanilla references\n- Cleaned up web/web.go to remove vanilla embed and routes\n- Verified build and tests pass\n\nCloses NK-2tcnmq

1 files changed, 0 insertions, 24 deletions

diff --git a/vanilla/node_modules/@exodus/bytes/encoding-browser.d.ts b/vanilla/node_modules/@exodus/bytes/encoding-browser.d.ts
deleted file mode 100644
index 565b43b..0000000
--- a/vanilla/node_modules/@exodus/bytes/encoding-browser.d.ts
+++ /dev/null
@@ -1,24 +0,0 @@
-/**
- * Same as `@exodus/bytes/encoding.js`, but in browsers instead of polyfilling just uses whatever the
- * browser provides, drastically reducing the bundle size (to less than 2 KiB gzipped).
- *
- * ```js
- * import { TextDecoder, TextEncoder } from '@exodus/bytes/encoding-browser.js'
- * import { TextDecoderStream, TextEncoderStream } from '@exodus/bytes/encoding-browser.js' // Requires Streams
- *
- * // Hooks for standards
- * import { getBOMEncoding, legacyHookDecode, labelToName, normalizeEncoding } from '@exodus/bytes/encoding-browser.js'
- * ```
- *
- * Under non-browser engines (Node.js, React Native, etc.) a full polyfill is used as those platforms
- * do not provide sufficiently complete / non-buggy `TextDecoder` APIs.
- *
- * > [!NOTE]
- * > Implementations in browsers [have bugs](https://docs.google.com/spreadsheets/d/1pdEefRG6r9fZy61WHGz0TKSt8cO4ISWqlpBN5KntIvQ/edit),
- * > but they are fixing them and the expected update window is short.\
- * > If you want to circumvent browser bugs, use full `@exodus/bytes/encoding.js` import.
- *
- * @module @exodus/bytes/encoding-browser.js
- */
-
-export * from './encoding.js'