All changes were behind the scenes which makes this release article a bit nerdy, but rest assured that even non-nerds will appreciate the improvements with how the plugin functions.
New WordPress Version Requirement
To pave the way for new and more native features, we bumped the minimum WordPress core version to
5.2.0 for both the basic and PRO versions of this plugin.
While this plugin won’t necessarily break on older versions of WordPress quite yet, we are no longer testing against WordPress core prior to
5.2.0 and could at any moment release a feature that breaks older versions of WordPress core.
Prior to version 5.0 of WordPress Core, any plugin which used React was required to include their own version of React. As of version 5.0, WordPress core started including React and ReactDOM as internal libraries.
We had a lot of internal discussion on how to approach using React with the modern version of WordPress core. Ultimately we opted to use React’s official CDN to include an external version of React that we could lock our package manager to.
With plugin stability being our top priority, here were our conclusions for our approach:
- WordPress core changes its version of React every couple of releases so if we used the included version we can’t guarantee forward compatibility with older versions of our plugins.
- Bundling React within our packages does not allow for browser caching between bundle versions.
- Using the official CDN adds a high probability of the library already existing in a user’s browser cache and requires no downloading.
- We maintain the ability to update our version of React anytime we need to without concern of conflict with WordPress core.
Debug Endpoint Improvements
To go along with the new WordPress version requirement, we added information about the WordPress version to the response to the debug endpoint. This will assist us when troubleshooting a user’s site.