Raven Scott e6658d4421 fix(pwa): resolve proxy connection reset and manifest same-origin warnings ...

Fix "Proxy error: connection reset by peer" caused by dashboard-server.js
looking for files in native-host/ instead of extension/dashboard/. Remove
the devBasePath parameter and resolve DEV_DASHBOARD_DIR directly from
__dirname so dev and distribution mode both find the correct files.

Fix all manifest warnings (start_url/id/scope/protocol_handlers ignored)
by reverting manifest.webmanifest to relative/extension-origin URLs for
the chrome-extension:// context, and having dashboard-server.js dynamically
generate a manifest at /manifest.webmanifest with absolute
https://my.dash.board/ URLs — satisfying Chrome's same-origin requirement
for PWA installability.

Also serve extension icons at https://my.dash.board/icons/<file> with
correct bundle key mapping, and embed them in the distributable binary
via build-distributable.js.

2026-03-01 03:10:11 -05:00

..

logger.js

refactor(native-host): modularize host.js and holesail-manager.js

2026-02-28 23:15:08 -05:00

message-router.js

feat(pwa): experimental — add my.dash.board virtual host for secure PWA install

2026-03-01 02:58:52 -05:00

paths.js

refactor(native-host): modularize host.js and holesail-manager.js

2026-02-28 23:15:08 -05:00

startup.js

fix(pwa): resolve proxy connection reset and manifest same-origin warnings

2026-03-01 03:10:11 -05:00