Weston Ruter

The customizer is a single-page application that includes a lot of events, messages, and state changes which drive the application. Being aware of these things is essential for developing JavaScript for the customizer.
To use, activate the plugin, open the customizer and the browser console and enter:
<pre>
CustomizerDevTools.startLogging()
</pre>
You can then either start interacting with the customizer app to see the log entries from that point, or you can reload the customizer to see the log entries emitted during the customizer initialization.
Not everything in the customizer is currently implemented to emit a log entry. File an issue for any specific event that may be needed.
Features:
<ul>
<li>Start logging of customizer events via running <code>CustomizerDevTools.startLogging()</code> from your browser console, and stop via <code>CustomizerDevTools.stopLogging()</code>. In the former, you can filter what is logged out by passing a string or regular expression (<code>RegExp</code> object) to match against the given log, or you can use the browser console’s built-in log filtering.</li>
<li>Logs out all events triggered on <code>wp.customize</code>.</li>
<li>Logs out additions and changes to to <code>wp.customize.state</code>.</li>
<li>Logs changes to the <code>active</code> and <code>expanded</code> states for panels, sections, and controls.</li>
<li>Logs out messages sent and received by the pane (controls) and preview.</li>
<li>Logs out dynamic addition and removal of panels, sections, controls, partials, and settings (after the <code>ready</code> event triggers).</li>
<li>The <code>wp.customize</code> object from the Customizer preview is made persistently available from the parent frame via <code>CustomizerDevTools.previewCustomize</code>. This reference is updated whenever the preview refreshes, so you no longer have to change the frame window context to access this object.</li>
<li>In the same way, the current Customizer preview <code>window</code> is exposed as <code>CustomizerDevTools.previewWindow</code>. This is a shortcut for doing <code>wp.customize.previewer.targetWindow.get()</code>, and it has the added benefit of allowing the browser’s dev tools to provide auto-completion.</li>
</ul>
Make sure you also install the <a href="https://github.com/xwp/wp-customizer-browser-history" rel="nofollow ugc">Customizer Browser History</a> and <a href="https://github.com/xwp/wp-customize-snapshots" rel="nofollow ugc">Customize Snapshots</a> plugins so that you can reload the browser window and have the Customizer load with the same state as before you reloaded, including the persistence of the focused panel, section, control, the previewed URL, the scroll position in the preview, and which device is being previewed.
Requires PHP≥5.3.

Customizer Dev Tools

Tools for facilitating JavaScript development in the customizer.

Brad Parbs

Display your WordPress site’s environment type in the admin bar.
<h3>Available Filters</h3>
‘where_env_should_add_env_type’ – Defaults to true if the user is an admin and the admin bar is showing. Filter this to allow different roles to view as well. 
‘where_env_environment_type’ – Modify the environment type. You’ll also need to use this filter if you’re running an older version of WP that doesn’t have the ‘get_environment_type’ function. 
‘where_env_styles’ – An array of colors/icons to use for the different environment types.

Where

Thumbs up!

A WordPress plugin to display your site's environment type in the admin bar.

Customizer Dev Tools vs Where