Older posts from the archive.
The settings-page-as-SPA approach: routing, the data store, REST endpoints, and nonce handling without dragging in a second state library.
A lean build setup that respects WordPress bundled dependencies and keeps your sanity intact. Config, externals, aliases, and the dev loop.
They solve overlapping problems. Here is the decision tree I use on client work, and where each one quietly falls down.
Two islands, one page, no Redux. How to keep independent React roots in sync using @wordpress/data, custom events, and the occasional shared context.
No posts match this filter yet.