removing crappy browser test. Not that useful to anyone

Author: willwade

docs/BROWSER_USAGE.md

@@ -565,14 +565,7 @@ async function safeLoadFile(file) {
 
 ## Testing
 
-See [Browser Test Page](../examples/browser-test.html) for interactive testing.
-
-To run the test server:
-```bash
-node examples/browser-test-server.js
-```
-
-Then open: http://localhost:8080/examples/browser-test.html
+Use the Vite demo in `examples/vitedemo` for interactive browser testing.
 
 ## Troubleshooting
 
@@ -614,5 +607,4 @@ await processor.loadIntoTree(uint8Array);
 
 - [API Documentation](./API.md)
 - [Examples](../examples/)
-- [Browser Test Page](../examples/browser-test.html)
-- [Test Server](../examples/browser-test-server.js)
+- [Vite Browser Demo](../examples/vitedemo)

examples/README.md

@@ -49,79 +49,7 @@ These pagesets are used by:
 
 To run demo scripts that use these pagesets, see the [scripts/README.md](../scripts/README.md).
 
-## Browser Testing
+## Browser Demo (Vite)
 
-### ⚠️ Important Note
-
-AACProcessors is built with TypeScript and outputs CommonJS modules. To use it in a browser, you **must use a bundler** (Vite, Webpack, Rollup, etc.). The browser test page below only validates the library structure - it cannot run actual processors without a bundler.
-
-### Browser Test Page
-
-A dedicated browser test page is available for validating the library structure:
-
-**Start the test server:**
-```bash
-node examples/browser-test-server.js
-```
-
-**Open in your browser:**
-```
-http://localhost:8080/examples/browser-test.html
-```
-
-**What it tests:**
-- ✅ Browser build files exist and are accessible
-- ✅ Type definitions are present
-- ✅ Processor exports are available
-- ❌ **Does NOT run actual processors** (requires bundler)
-
-### What Gets Tested
-
-The browser test page (`browser-test.html`) verifies:
-
-1. **Module Loading** - Can the browser load the ES modules?
-2. **Factory Functions** - Do `getProcessor()` and `getSupportedExtensions()` work?
-3. **Processor Instantiation** - Can processors be created?
-4. **File Loading** - Can files be loaded from `<input type="file">`?
-5. **Buffer Handling** - Do ArrayBuffers/Uint8Arrays work correctly?
-6. **Tree Structure** - Can AACTree be created from files?
-7. **Text Extraction** - Can texts be extracted from files?
-
-### Supported File Types in Browser
-
-The browser test page supports all browser-compatible processors:
-
-- **DotProcessor** (.dot) - OpenSymbols Board files
-- **OpmlProcessor** (.opml) - OPML outline files
-- **ObfProcessor** (.obf/.obz) - Open Board Format files
-- **GridsetProcessor** (.gridset) - Grid 3 gridset files (not .gridsetx)
-- **ApplePanelsProcessor** (.plist) - Apple Panels files
-- **AstericsGridProcessor** (.grd) - Asterics Grid files
-
-### Manual Testing
-
-1. Open the browser console (F12 or Cmd+Option+I)
-2. Click "Select a file to test" to upload an AAC file
-3. Click "Test File" to process it
-4. Check the results panel for page count, button count, and extracted texts
-
-### Automated Tests
-
-Click "Run All Browser Tests" to run automated checks:
-- Factory function tests
-- Extension support tests
-- Processor instantiation tests
-- Buffer handling tests
-
-### Node-Only Processors
-
-The following processors are **not available** in the browser:
-- **SnapProcessor** (.spb/.sps) - Requires SQLite
-- **TouchChatProcessor** (.ce) - Requires SQLite
-- **ExcelProcessor** (.xlsx) - Uses fs at top level
-
-### Notes
-
-- Gridset `.gridsetx` files (encrypted) are not supported in browser
-- All processors work with Buffer, Uint8Array, and ArrayBuffer inputs
-- File paths are not supported in browser (use file inputs or fetch)
+For browser testing, use the Vite demo in `examples/vitedemo`. It bundles the
+library and exercises real processors in a browser environment.

examples/browser-test-server.js

@@ -35,8 +35,7 @@ The demo will open automatically at: http://localhost:3000
 This demo is intended for `npm run dev` only. The production build currently fails because the
 demo source includes strict TypeScript issues, so it will not work "out of the box."
 
-If you need a no-build browser check, use the browser test page served by:
-`node examples/browser-test-server.js`
+This demo is the recommended browser test environment.
 
 ## How to Use