mirror of
https://github.com/home-assistant/frontend.git
synced 2026-08-16 10:02:41 +01:00
22ca986cce
The gallery build is the only e2e build that still emits source maps: unlike demo and the e2e test app, `bundle.config.gallery` never accepted `isTestBuild`, so the production build always used `nosources-source-map` — even though the artifact is only ever loaded by Playwright. The e2e run's gallery artifact contains 693 `.map` files (14 MB of a 105 MB dist); the demo artifact, which already passes `is-test`, contains none. Thread `isTestBuild` through the gallery config and set `is-test: true` for the e2e gallery build, so those maps are no longer generated. The design deployment and preview workflows do not set `IS_TEST`, so they keep their source maps. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Bundling Home Assistant Frontend
The Home Assistant build pipeline contains various steps to prepare a build.
- Generating icon files to be included
- Generating translation files to be included
- Converting TypeScript, CSS and JSON files to JavaScript
- Bundling
- Minifying the files
- Generating the HTML entrypoint files
- Generating the service worker
- Compressing the files
Converting files
Currently in Home Assistant we use a bundler to convert TypeScript, CSS and JSON files to JavaScript files that the browser understands.
We currently rely on Webpack. Both of these programs bundle the converted files in both production and development.
For development, bundling is optional. We just want to get the right files in the browser.
Responsibilities of the converter during development:
- Convert TypeScript to JavaScript
- Convert CSS to JavaScript that sets the content as the default export
- Convert JSON to JavaScript that sets the content as the default export
- Make sure import, dynamic import and web worker references work
- Add extensions where missing
- Resolve absolute package imports
- Filter out specific imports/packages
- Replace constants with values
In production, the following responsibilities are added:
- Minify HTML
- Bundle multiple imports so that the browser can fetch less files
- Generate a second version that is ES5 compatible
Configuration for all these steps are specified in bundle.js.