The current import-only root exports make Bun require(@stacksjs/ts-validation) fail with Cannot find module, even though the declared package is installed. This breaks lazy message-provider loading in Stacks validation and the isolated HQ profile/equipment/input regression. Keep validation off routes that do not use it; do not replace the lazy caller with an eager import. Add an explicit Bun condition for the existing ESM build, and verify real packaged dist consumers in both require-first and import-first order share the same validator and message-provider singleton. Actual packaged baseline: two failures before the export fix. Require normal patch publication and actual consumer installation. Related: https://github.com/stacksjs/stacks/issues/3140 and https://github.com/stacksjs/hq.training/issues/346.
Expose the published root entry to Bun synchronous loading
#1110The normal 0.5.7 release is published. A framework consumer using that published dependency passes all 267 validation/router checks (604 assertions), including the unchanged router import-graph guard. The separate packaged consumer exercises built @stacksjs/validation/messages outside application aliases; it passes with the synchronous provider lookup restored. Full framework type checks pass; Pickier reports zero errors and four pre-existing changelog warnings.
Source fix: https://github.com/stacksjs/stacks/commit/e5f65db358 Framework publication remains tracked by /stacks/stacks/issues/3140.
Sign in to comment on this issue.