Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchIf your Forge macro logs Uncaught (in promise) Error: Unable to emit ready event. in the browser console, the most likely cause is older @forge/bridge behavior. A secondary investigation reports that the library throws when a follow-up bridge call made by view.emitReadyEvent() is unsupported in normal Confluence page view. It also reports that @forge/bridge 5.13.0 stopped throwing. The fix is to upgrade. If you can’t upgrade yet, catch the rejection.
Atlassian’s own documentation covers the API and the manifest flag. It does not mention this error or confirm the fix version, so the version details below are labeled as secondary-source reporting.
As an Amazon Associate I earn from qualifying purchases.
What emitReadyEvent is for
Atlassian describes view.emitReadyEvent() as a call that “notifies Confluence that a Forge macro has completed loading and is ready for export or further processing.” It uses the Forge Events API to emit an EXTENSION_READY event that carries context about the macro. PDF export is the named consumer. With the signal, export can detect fully loaded macros without scanning the DOM or guessing at timing. Source: Forge bridge view API.
Recommended Free Tools
How to configure it
1. Enable the manifest flag
In the macro module, emitsReadyEvent is optional and defaults to false. Set it to true if your macro will send the event. See the Forge macro module reference.
#1 Best Overall
2. Call it after the work is done
Atlassian’s example fetches data, stores the result, does any other work the macro needs, and only then calls await view.emitReadyEvent(). Follow that order. Call it once the content you want exported is ready, not at mount time.
What the error means
A LeanZero article dated September 18, 2026 reports the following. I could not check these implementation details against the package source.
Rank #2
- Used Book in Good Condition
- In
@forge/bridge5.10.2 through 5.12.0, the function first gets the macro context and emitsEXTENSION_READY. - It then makes a separate bridge call. In ordinary page view that call can be unsupported, and in those versions a rejected or false result threw “Unable to emit ready event.”
- So the readiness event had already been sent when the error appeared.
The error therefore doesn’t by itself show that PDF export is broken. Atlassian’s pages don’t describe this failure mode either way.
How to fix it
Upgrade @forge/bridge
Check the installed version with npm ls @forge/bridge, then update to a current release compatible with your app. The same article reports that 5.13.0 removed the thrown error and that later versions silently handle the unsupported call in normal view. Treat 5.13.0 as the reported boundary, not an officially confirmed one.
Rank #3
If you can’t upgrade yet: catch the rejection
try {
await view.emitReadyEvent();
} catch (e) {
// Reported older-bridge behavior: the event was already emitted.
console.debug('emitReadyEvent follow-up call failed', e);
}The article recommends this as safe because the event was sent first. That is the article’s advice, not documented Atlassian error handling. Keep the call itself, because removing it would drop the readiness signal.
Quick triage
| Question | If yes | If no |
|---|---|---|
| Is the bridge version between 5.10.2 and 5.12.0 (reported range)? | Upgrade, or wrap the call in try/catch. | Re-check the installed version; the error may come from something else. |
| Does the macro need to signal readiness for export? | Set emitsReadyEvent: true and call the API. |
The flag defaults to false; you may not need the call. |
| Does the call happen after data and rendering are complete? | Fine. | Move it after the work that produces the exportable content. |
Export caveats
Don’t assume emitReadyEvent fixes every export format. Users in the Atlassian Developer Community thread “When is emitReadyEvent needed?” (August–September 2025) report that PDF and Word export can behave differently. Those are anecdotes, not product guarantees. The same thread asks whether emitting before response generation finishes is correct. Per Atlassian’s example, it isn’t: emit after the work completes.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
