You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(console): bundle THIS framework's client into the vendored console
The console SPA inlines @objectstack/client, and the version came from
objectui's own lockfile — which necessarily lags the framework whenever
a release adds new client APIs (the new client isn't on npm when
objectui's lockfile is written). 11.5.0 shipped the new import UI
bundled against client 11.2.0, so the console threw "The connected
@objectstack/client does not support async import jobs." at runtime.
build-console.sh now exports OBJECTSTACK_CLIENT_DIST=packages/client so
vite aliases the bundled client to this repo's own build — the bundled
client always matches the framework release, eliminating the
framework → objectui pin-bump → framework re-release round-trip.
Details:
- Fail hard if the pinned objectui SHA lacks the vite.config.ts hook.
- Build the client dist first if missing.
- Split the build: deps via turbo, the console app via its own build
script directly — turbo v2 strict env strips undeclared vars, which
is exactly how the first injection attempt silently produced a stale
bundle.
- Post-build canary (CONSOLE_BUNDLE_CANARY, default 'import/jobs')
asserts the fresh client actually landed in dist/assets.
Verified: rebuilt at the currently pinned SHA 1432efe81 (whose lockfile
still resolves client 11.2.0) — dist now contains the import/jobs
routes; before this change it had zero occurrences.
Fixes#2512
0 commit comments