build: ship the full IIFE bundle and vendor every lockstep package in the Full ZIP - #731
Merged
Conversation
… the Full ZIP The all-in-one IIFE (core plus every extension except react) was built only behind EXOJS_FULL_BUNDLE=1 and then went nowhere: not in the npm files list, not a release asset, not in the Full ZIP. A script-tag consumer had the core and no path to any extension. The production build now always emits exo.full.iife.js and its minified twin, the tarball ships them, size-limit budgets the minified one at 550 KB gzipped (measured 524 KB), and the deployment guide points at the jsDelivr URL. The Full ZIP vendored six of the twelve extensions, copied out of the built site's vendor directory through a hand-kept list. It now reads every lockstep package's own dist/esm, so the set is derived from the release matrix, and puts Core's single-file bundles beside the ESM tree under vendor/exojs. A test pins that bundle list to the tarball's files entries.
Exoridus
enabled auto-merge (squash)
September 11, 2026 22:25
Bundle ReportChanges will increase total bundle size by 19.37MB (59.94%) ⬆️
Affected Assets, Files, and Routes:view changes for bundle: site-server-esmAssets Changed:
Files in
App Routes Affected:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
EXOJS_FULL_BUNDLE=1and then went nowhere: not in the npmfileslist, not a release asset, not in the Full ZIP. A script-tag consumer had the core and no path to any extension. The production build now always emitsexo.full.iife.jsand its minified twin, the tarball ships them,size-limitbudgets the minified one at 550 KB gzipped (measured 524 KB), and the deployment guide points at the jsDelivr URL.dist/esm, so the set is derived from the release matrix, and puts Core's single-file bundles beside the ESM tree undervendor/exojs/. A test pins that bundle list to the tarball'sfilesentries.Validation
pnpm gates typecheck,pnpm gates site,test/release/full-zip.test.ts,pnpm size, Prettier, ESLint,git diff --check