Types package: Node ESM compatibility (1.64.0)

The npm package @vonq/hapi-elements-types is now 1.64.0. This release improves Node.js ESM compatibility while keeping the same root import for most use cases.

What changed

• Browser and bundlers (Vite, webpack, Next.js client, and similar) keep using the full barrel: import from @vonq/hapi-elements-types. Tools that set the browser export condition use the full published entry; otherwise the default import entry is still the full surface (including _window / window.hapi typings).
• Node (scripts, CLIs, tooling) should also import from @vonq/hapi-elements-types. Node applies the node export condition and loads a Node-specific build of the package so native ESM resolution works. That build exposes the same module list except that _window is re-exported as types only at the package entry (export type *), not as runtime values from the barrel.
• Explicit Node entry: you may import @vonq/hapi-elements-types/node if you want the same module as the node condition without relying on conditional exports.

No change is required for typical front-end or bundled code that already uses named imports from the package root. Optional /node is only relevant for Node-side TypeScript or JavaScript that benefits from the Node-specific build.

References

• npm: the @vonq/hapi-elements-types package page and its README describe import patterns (browser vs Node, /node).

Version

• @vonq/hapi-elements-types: 1.64.0