theme-relative destination path * (e.g. 'assets/hero-9c8d7e6f.png'). Never touched by this class — * the installer performs the actual file copy. * * @var array */ public $copy_manifest = array(); /** * Newline-separated PHP source, one wp_enqueue_style()/ * wp_enqueue_script() call per line, destined for functions.php. * * @var string */ public $enqueue_php = ''; /** * The Parsed_Document's body_html with local asset references * rewritten to `` snippets pointing at the theme's * assets/ directory. External/data URLs are left untouched. * * @var string */ public $body_html = ''; /** * Theme-relative destination path => rewritten CSS content, for * copied stylesheets whose own root-relative url(...) references * needed fixing up. A caller writing out copy_manifest should prefer * this content over a raw copy for any dest path that appears here. * * @var array */ public $css_rewrites = array(); /** * Theme-relative destination path => rewritten JS content, for copied * script chunks whose embedded Vite modulepreload helper needed * fixing up — see Asset_Rewriter::rewrite_vite_preload_base(). A * caller writing out copy_manifest should prefer this content over a * raw copy for any dest path that appears here. * * @var array */ public $js_rewrites = array(); /** * Site-root-relative request paths (e.g. 'logo.ico' or * 'assets/hero-abc123.png') for "passthrough" files copied through * whose references live only inside compiled JS and so couldn't be * rewritten directly. Theme_Generator uses this list to build a small * request interceptor that serves them back at those exact paths * regardless of where in the code they're referenced from. * * @var string[] */ public $root_files = array(); /** * Enqueue handles for scripts whose original