ChangelogVersion 4.7
Types package: barrel-only imports
Types package: barrel-only imports
Breaking change
The published npm package @vonq/hapi-elements-types now exposes a single entry point only. Subpath imports such as @vonq/hapi-elements-types/alert/enums are no longer supported.
Migration
Use named imports from the package root:
import { AlertKey, WindowHapiModuleName } from "@vonq/hapi-elements-types"If you still have long relative paths into a copied types tree, run the migrate CLI (see below). Preview changes, then apply:
npx @vonq/hapi-elements-types-migrate --dry-run
npx @vonq/hapi-elements-types-migrateMigrate CLI (@vonq/hapi-elements-types-migrate)
Default command runs normalize-types-module-specifiers, which rewrites legacy module specifiers to the barrel import (@vonq/hapi-elements-types).
| Command / option | Description |
|---|---|
| (default) | Run the default migration on the current directory (or pass directories). |
list | Print available migration ids (normalize-types-module-specifiers, alias remove-types-dist-imports). |
run <migration-id> [dirs...] | Run a named migration; optional directories to scan (default: .). |
--dry-run | Print which files would change without writing. |
--help, -h | Show usage. |
Examples:
npx @vonq/hapi-elements-types-migrate --dry-run
npx @vonq/hapi-elements-types-migrate ./src
npx @vonq/hapi-elements-types-migrate list
npx @vonq/hapi-elements-types-migrate run normalize-types-module-specifiers ./srcInstall @vonq/hapi-elements-types from npm and import from the package root. Aside from the documented @vonq/hapi-elements-types/node entry (Node tooling), do not use other subpath imports (@vonq/hapi-elements-types/...).