AXE-WEB/bridgeable-build
1
0
Fork 0
Code Pull Requests Activity

Emit hashed static assets in Bridgeable builds

Browse Source
This commit is contained in:
Roman Axelrod
2026-06-05 13:34:17 -06:00
parent 8055a15ea3
commit c19d0d7182
3 changed files with 123 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1
View File
@@ -53,6 +53,7 @@ The CLI preserves the current Bridgeable Components production contract:
- Section CSS and JS are emitted as standalone hashed assets.
- Component CSS is expected to be imported by global CSS or section CSS.
- Component JS is emitted only when it self-registers with `window.initBlock`.
- Static image, font, and video assets are emitted as hashed files and added to `manifest.json`.
- `*.twig` and `*.component.json` files are copied into the output.
- Storybook-only files, fixture data, docs, build config, `node_modules`, `.git`, and previous build output are excluded.
- Vite emits `manifest.json`, which the WordPress Bridgeable Components plugin uses to resolve hashed asset filenames.