faustjs VS php-scoper

Yeah, in hindsight, we would have used Next/Vercel. So we're tactically moving over to that. There are many new frameworks, like Astro, that are really exciting, but it seems like Next is the best choice if you have a data-heavy app that has a dynamic mix of SSR and static pages. For Wordpress in particular, I'd recommend that you check out Faust.js. It's build with Next and I'm amazed by how well it works with Wordpress without much effort: https://faustjs.org/

https://faustjs.org is a great headless Wordpress solution for Nextjs. I've tried several CMS solutions and ultimately WordPress is invariably the friendliest option from a client perspective.

I'm working through a large project where we're leveraging WordPress and Next.js. Check out Faust.js (https://faustjs.org/) which works as a layer to handle a lot of the query/template/routing stuff that maybe isn't super-intuitive when trying to hook WordPress up headlessly...

- FaustJS (built for headless WP on NextJS w/ full site editing capabilities)

Faust.js is the front-end JavaScript framework built on top of Next.js, created to make developing headless WordPress sites easier. The idea of this new version is to make a parity between the WordPress world that a developer might be used to but replicate it as much as possible in the JavaScript front-end world.

This is where it started. Then there is also Faustjs started by WPEngine. https://faustjs.org/

https://faustjs.org/ built specifically for headless WP

return [ 'patchers' => [ function ( $file_path, $prefix, $contents ) { /* * There is currently no easy way to simply whitelist all global WordPress functions. * * This list here is a manual attempt after scanning through the AMP plugin, which means * it needs to be maintained and kept in sync with any changes to the dependency. * * As long as there's no built-in solution in PHP-Scoper for this, an alternative could be * to generate a list based on php-stubs/wordpress-stubs. devowlio/wp-react-starter/ seems * to be doing just this successfully. * * @see https://github.com/humbug/php-scoper/issues/303 * @see https://github.com/php-stubs/wordpress-stubs * @see https://github.com/devowlio/wp-react-starter/ */ $contents = str_replace( "\\$prefix\\_doing_it_wrong", '\\_doing_it_wrong', $contents ); $contents = str_replace( "\\$prefix\\__", '\\__', $contents ); $contents = str_replace( "\\$prefix\\esc_html_e", '\\esc_html_e', $contents ); $contents = str_replace( "\\$prefix\\esc_html", '\\esc_html', $contents ); $contents = str_replace( "\\$prefix\\esc_attr", '\\esc_attr', $contents ); $contents = str_replace( "\\$prefix\\esc_url", '\\esc_url', $contents ); $contents = str_replace( "\\$prefix\\do_action", '\\do_action', $contents ); // ... } ] ]

🍾 GraphQL API for WordPress is now scoped, thanks to PHP-Scoper! describes a strategy to scope a WordPress plugin using PHP-Scoper, as to avoid conflicts with other plugins.