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 packages/commonInstall @vonq/hapi-elements-types from npm and import from the package root only; do not rely on subpath imports (@vonq/hapi-elements-types/...).
Release candidates (testing before stable)
npm latest is what plain yarn add @vonq/hapi-elements-types installs. Release candidates are published under a separate dist-tag (e.g. rc) so testers can opt in without changing default installs.
- To try a types RC:
yarn add -D @vonq/hapi-elements-types@rcor an exact version such asyarn add -D @vonq/hapi-elements-types@1.62.0-rc.0. - To try a migrate CLI RC when published:
npx @vonq/hapi-elements-types-migrate@rcor pin@vonq/hapi-elements-types-migrate@rcin devDependencies.
Anyone who pins an exact RC version or uses @rc can still install the prerelease; unconstrained installs keep following latest.
Versioning (npm packages)
@vonq/hapi-elements-types: stable release lines follow the published types version (e.g. 1.62.0 after RC testing).@vonq/hapi-elements-types-migrate: the next feature line is 1.1.0 after 1.1.0-rc.* prereleases.
VONQ maintainers
Publishing, dist-tags, yarn scripts (publish:types, publish:types:rc, publish:migrate, publish:migrate:rc), and the full publishing checklist (before/after publish, deprecating old RCs, monorepo resolutions) live in the internal DOCS.md in the monorepo (## Types package → How to publish types package).
I18n
No translation keys changed.