Skip to content

fix: bug: Automatic publicPath is not supported in this browser - #811

Draft
SillyZir wants to merge 1 commit into
onbloc:mainfrom
SillyZir:auto-fix/783
Draft

fix: bug: Automatic publicPath is not supported in this browser#811
SillyZir wants to merge 1 commit into
onbloc:mainfrom
SillyZir:auto-fix/783

Conversation

@SillyZir

@SillyZir SillyZir commented Apr 3, 2026

Copy link
Copy Markdown

Summary

Set an explicit publicPath in the webpack output configuration to prevent the "Automatic publicPath is not supported in this browser" error that crashes the Adena extension on simple web pages.

Fixes #783

Problem

When visiting pages with minimal JavaScript (e.g., no <script src> tags or simple sites like example.com), webpack's runtime could not automatically determine the publicPath from document.currentScript, causing the extension to crash with Uncaught Error: Automatic publicPath is not supported in this browser.

Solution

Added an explicit publicPath property to the output configuration in packages/adena-extension/webpack.config.js, removing the reliance on webpack's automatic public path detection. The manifest generation was also cleaned up to directly reference packageInfo.description and packageInfo.version instead of spreading parsed content, improving clarity.

Impact

The Adena extension will no longer crash on pages with minimal or no script tags, restoring functionality across Chrome, Brave, and Edge on all websites regardless of their JavaScript usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: Automatic publicPath is not supported in this browser

1 participant