OmniRoute/changelog.d/fixes/pack-entrypoint-closures.md at feat/plugin-browser-pool

mirror of https://github.com/diegosouzapw/OmniRoute.git synced 2026-07-26 09:52:11 +03:00

Files

Diego Rodrigues de Sa e Souza 9767b7eb34 test(build): derive pack-artifact closures for all npm-shipped entrypoints (#7065 class) (#7081 )

The server-ws closure test hardcoded ONE wrapper and ONE import form. This
generalizes it: every dist-root wrapper in EXTRA_MODULE_ENTRIES that ships in
the npm channel has its local imports (static, dynamic import(), require())
required in both APP_STAGING_ALLOWED_EXACT_PATHS and PACK_ARTIFACT_REQUIRED_PATHS,
and the bin/omniroute.mjs CLI boot path is closure-checked too — its direct
imports bin/cli/data-dir.mjs and bin/cli/utils/storageKeyProvision.mjs were
only covered by an allowlist PREFIX (absence from the tarball had no gate) and
are now required paths. TDD: the bin closure test failed on those two before
the policy fix.

2026-07-14 03:55:29 -03:00

479 B

Raw Permalink Blame History

Packaging: pack-artifact closure tests now cover EVERY npm-shipped dist wrapper (derived from EXTRA_MODULE_ENTRIES) and the bin/omniroute.mjs CLI entry — including dynamic import() and require() forms the original server-ws test missed — requiring each local import in both the prepublish prune allowlist and check:pack-artifact; bin/cli/data-dir.mjs and bin/cli/utils/storageKeyProvision.mjs are now required tarball paths (#7065 class hardening, WS1.1)

479 B Raw Permalink Blame History

479 B

Raw Permalink Blame History