Failed to forward message of type "${packet.type}" from "${p

Error message

Failed to forward message of type "${packet.type}" from "${packet.from}" to "${packet.to}".

What it means

When the bridge receives a packet addressed to a different port (packet.to !== this.portName), it forwards it via #sendPacket to the target. If that forwarded postMessage fails, it warns with the packet type/from/to details and sends a failure response back to the original sender.

Source

Thrown at app-vite/exports/bex/private/bex-bridge.js:656

      this.log(
        'Received a message that does not appear to be emitted by a Quasar bridge or is malformed.',
        packet
      )
      return
    }

    this.log(
      `Received message of type "${packet.type}" from "${packet.from}".`,
      packet
    )

    /**
     * if the packet is not addressed to this bridge
     * then forward it to the target
     */
    if (packet.to !== this.portName) {
      this.#sendPacket(packet).catch(err => {
        this.warn(
          `Failed to forward message of type "${packet.type}" from "${packet.from}" to "${packet.to}".`,
          err
        )

        this.#sendMessage({
          id: packet.id,
          to: packet.from,
          messageType: 'event-response',
          messageProps: {
            error: {
              message: err.message,
              stack: err.stack || 'no stack available'
            },
            quiet: true
          }
        })
      })
      return

View on GitHub (pinned to 4841521b5f)

Solutions

Ensure the receiving context (target port) is open and has created its bridge before sending
Re-check that the `to` address matches an active bridge port name
Reopen/reload the closed context (popup, content script tab) and retry the message
Handle the failure response sent back to the sender (packet with error) gracefully

Example fix

// before
bridge.send('do.work', payload) // target page may be closed
// after
try {
  const res = await bridge.send('do.work', payload)
} catch (err) {
  console.warn('Receiver unavailable, retry later', err)
}

Defensive patterns

Strategy: retry

Validate before calling

// ensure the target context has an active bridge before routing
// sender side: verify the addressee is reachable
function canRouteTo(knownPorts, to) {
  return knownPorts.includes(to)
}

Try / catch

try {
  await bridge.send('target.event', payload)
} catch (err) {
  // receiver closed; recreate bridge/ports then retry once
  await reopenBridge()
  await bridge.send('target.event', payload)
}

Prevention

Only send messages to contexts you know are alive (check port readiness)
Recreate ports after MV3 service-worker restarts and page reloads
Handle the error response packet the bridge sends back to the sender
Avoid messaging popups/options pages that may close at any moment

When it happens

Trigger: A message arrives at a bridge whose port is not the addressee and the forwarding #sendPacket (port.postMessage) throws — usually the target port is disconnected, its counterpart context closed, or the port was never opened.

Common situations: Content script or popup closed while a message was in flight; dev server hot-reload restarted the extension page killing ports; message routed to a listener name that doesn't exist in the target context.

Related errors

AI-assisted analysis of quasarframework/quasar@4841521b5f (2026-08-30). Data as JSON: /api/errors/f7dedaacd796cc61. Report an issue: GitHub.