6.1.1 · 2026-08-23
Honor the declared validator dependency under consumer conflicts
The release resolves strong-type through the package boundary while preserving one Node/browser source.
Resolution
- Bare
strong-typeimport selects event-pubsub's nested exact 2.0.0 before a conflicting consumer root. - Bundlers may use the explicit browser entry; native browsers select the same source through an import map.
- Unbundled native ESM requires no build step, with normal and scoped-conflict maps documented.
Evidence
- Packed Node consumers poison root
strong-type1.1.0 and prove nested 2.0.0 executes through ESM and CommonJS. - Packed real-Chrome consumers execute both maps, and Rollup 4.62.5 with node-resolve 16.0.3 bundles the same conflict fixture.
- 131 shared checks include 12 Given/When/Then workflows resolved through the bare package map in Chrome.