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.
Extension stats
By: wille.eklund
Users: 4,000+
Rating: 4.58
(12)
Creation date: 2018-11-23
Risk impact: Low risk impact
Risk likelihood: Low risk likelihood
Manifest version: 2
Size: 3.70K
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.
Extension summary
This chrome extension prints messages sent with postMessage to the console for debugging.
User reviews
Pros
- Very convenient for the development process.
- Useful for debugging postMessage functionality.
- Logs events sent to iframes as well as those received by the top frame.
- Works as advertised and does what is needed.
- Saves time for developers.
Cons
- Some users reported it not working at all.
- Difficulties in toggling off logging without disabling the entire extension.
- Need for more information in the MessageEvent logs (e.g., origin, source).
- Verbose log setting is not prominently mentioned in the description.
Most mentioned
- Check 'Verbose' in Console tab's top bar 'Default levels' to see logs.
- Works as expected and logs events.
Recent reviews
Thank you, very convenient for development process.
This extension is great! Use it a lot.
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.
Extension safety
Risk impact
postMessage debugger requires very minimum permissions.
Risk likelihood
postMessage debugger has earned a fairly good reputation and likely can be trusted.
Upgrade to see risk analysis details
Similar extensions
Here are some Chrome extensions that are similar to postMessage debugger:
postMessage Developer Tools post-message-logger tweak: mock and modify HTTP requests postMessage-catcher Disable Content-Security-Policy BrowserStack Analytics Debugger ModHeader - Modify HTTP headers MobX Developer Tools Web Vitals Requestly - Intercept, Modify & Mock HTTP Requests CORS Unblock
alxHenry Developer
5.00
3,000+
inisomniac1426
3.00
78
https://tweak-extension.com
4.68
50,000+
yangjin
3.00
1,000+
Phil Grayson
3.64
50,000+
https://www.browserstack.com
2.94
100,000+
https://www.thyngster.com
4.59
100,000+
https://modheader.com
3.15
800,000+
Andy Kogut
3.35
20,000+
addyosmani
4.21
100,000+
https://requestly.com
4.34
200,000+
balvin.perrie
4.17
200,000+