postMessage debugger

This extension prints messages sent with postMessage to the console

What is postMessage debugger?

"postMessage debugger" is a Chrome extension developed to assist in the debugging process by capturing and printing messages that are sent using the postMessage function to the console. This tool aids developers in tracking message exchanges in the development environment for problem-solving and code verification.

Download

Stats

By: wille.eklund

View on Chrome Web Store

Users: 5,000+

Rating: 4.58 (12)

Version: 0.2.0 (Last updated: 2018-11-28)

Creation date: 2018-11-23

Risk impact: Low risk impact

Risk likelihood: Low risk likelihood

Manifest version: 2

Size: 3.70K

Stats date:

Chrome-Stats Rank

# 13511 ▲ 7

Other rankings

#5517 in Developer Tools ▲ 22 #43 in debug keyword 32 ▲ 3 #216 in messages keyword 35 ▲ 38

Other platforms

Not available on Firefox

Not available on Edge

Want to check extension ranking and stats more quickly for other Chrome extensions? Install Chrome-Stats extension to view Chrome-Stats data as you browse the Chrome Web Store.

Summary

Analyze keywords

This chrome extension prints messages sent with postMessage to the console for debugging.

User reviews

User reviews summary

These summaries are automatically generated weekly using AI based on recent user reviews. Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate, spammy, or outdated.

Pros

Convenient for development process
Can report messages sent to iframes
Not malicious

Cons

Lacks detailed information about each MessageEvent
Unable to toggle off the logging
Requires to set console log level to Verbose

Most mentioned

Useful tool for developers
Setting to 'Verbose' to see the logs
Works as advertised

Recent reviews

Thank you, very convenient for development process.

Валентин Ткачев, 2023-11-12

This extension is great! Use it a lot.

E. Donker, 2023-01-30

I was pleasantly surprised that this reports messages sent to iframes as well as messages received by the top frame as well. As others said, if you don't see anything in the devtools console, you probably need to pull out the sidebar to look at the verbose/debug log level. A good example case is the youtube embed API (you can find examples on codepen). It would be very helpful if this logged a bit more information about each MessageEvent rather than just the data...like the origin, source, ports and lastEventId. Currently it seems to log the window title, but perhaps the window url or origin would be more useful.