CSP and bundle size

The macro component mainline compiles the template during the build period, and does not require new Function when the browser is running, which is more suitable for strict CSP.

import { defineHtml } from "@elfui/core";

The main @elfui/core entry does not include the runtime compiler. The repository's current real tree-shaken application result is 9.72 KB gzip / 8.78 KB Brotli; the exact output depends on the imported APIs and bundler.

Release checks enforce four automated gzip/Brotli budgets: a real application, the complete Core facade, runtime, and reactivity. The real-application budget is 9.8 KB gzip / 8.9 KB Brotli. The Core facade intentionally includes every stable export to track the total public surface; its 16.5 KB gzip / 14.9 KB Brotli budget is not a typical application's download size. The build also verifies that production bundles remove DEV branches and that published ESM does not write a global __DEV__ flag.

Chain boundaries

@elfui/chain supports:

ElfUI.createComponent().template(`<button>{{ count }}</button>`);

This requires a runtime compiler, is approximately 21.19 KB in size, and may also hit tighter CSP limits. It is suitable for progressive embedding of old sites, small demos or low build constraint environments, and is not the main line of new projects.

Recommendations

TIP

Production applications are preferred:

1. Use the @elfui/core main entry.
2. Compile the macro component using @elfui/vite-plugin.
3. Limit chained components to ecosystem expansion or migration code.