just wondering if you ever considered making this generally compatible with web extens

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

considered web-extension polyfill? about chrome-extension-boilerplate-react-vite HOT 4 CLOSED

jonghakseo commented on May 14, 2024

considered web-extension polyfill?

from chrome-extension-boilerplate-react-vite.

Comments (4)

govza commented on May 14, 2024 2

Coming across the issue, it looks like web-extension polyfill is not needed anymore for manifest v3.
Firefox support though, achievable by small edition of manifest-parser (there is some small differences).

static convertManifestToString(manifest: Manifest): string {
    if (process.env.__FIREFOX__) {
      manifest = this.convertToFirefoxCompatibleManifest(manifest);
    }
    return JSON.stringify(manifest, null, 2);
  }

  static convertToFirefoxCompatibleManifest(manifest: Manifest) {
    const manifestCopy = {
      ...manifest,
    } as { [key: string]: unknown };

    manifestCopy.background = {
      scripts: [manifest.background?.service_worker],
      type: "module",
    };
    manifestCopy.options_ui = {
      page: manifest.options_page,
      browser_style: false,
    };
    manifestCopy.content_security_policy = {
      extension_pages: "script-src 'self'; object-src 'self'",
    };
    delete manifestCopy.options_page;
    return manifestCopy as Manifest;
  }

and

export default function customDynamicImport(): PluginOption {
  return {
    name: "custom-dynamic-import",
    renderDynamicImport() {
      if (process.env.__FIREFOX__) {
        return {
          left: `
        {
          const dynamicImport = (path) => import(path);
          dynamicImport(browser.runtime.getURL('./') + 
          `,
          // eslint-disable-next-line prettier/prettier
          right: ".split('../').join(''))}",
        };
      } ...