ReactWP 2.0.2

• Repair PageTransition and ASSETS
• Add filter rwp_no_critrical_medias
• Add default group named "all" for rwp_critical_medias, rwp_critical_fonts, rwp_no_critrical_medias. This group is called on pathname change

ReactWP v2.0.1

• Dynamize JavaScript Endpoint for themes
• Use term_id instead of ID for term route

ReactWP v2.0.0

This release represents a major refinement of ReactWP’s architecture.

Over the last two days, the framework has been pushed toward a more coherent hybrid model, where WordPress remains responsible for content and server context, while React handles runtime route state, transitions, and client-side rendering more cleanly.

What changed

• Route handling was reworked to better separate initial route boot data from active client-side route state
• A dedicated React route context was introduced to make runtime updates more consistent
• The loader was restructured to better coordinate critical asset download, display timing, and transition flow
• Media loading and rendering were improved for images, video, and audio
• Route payload handling was strengthened for pages, posts, users, and terms
• ACF integration was improved for non-post/page contexts such as authors and taxonomies
• Transition behavior was cleaned up to reduce timing conflicts and UI inconsistencies
• Loader and page transition animations are now easier to customize
• SEO/meta handling was improved during client-side navigation
• Multiple subtle bugs around empty groups, asset state, autoplay, and first-load timing were resolved

Result

ReactWP is now more stable, more extensible, and easier to reason about internally. This update lays stronger groundwork for the next phase of the framework.

ReactWP v1.0.0

ReactWP v1.0.0