Summary
Rename two v5 workspace packages — both the on-disk folder and the npm package name — for clearer, more descriptive naming.
| Current |
New |
packages/core (@commercelayer/core) |
packages/core-components (@commercelayer/core-components) |
packages/hooks (@commercelayer/hooks) |
packages/react-hooks-components (@commercelayer/react-hooks-components) |
Scope / affected areas
package.json name fields for both packages
workspace:* dependency declarations: react-hooks-components → core-components; react-components → both
- ~81
@commercelayer/core / @commercelayer/hooks import statements across react-components (src + specs) and hooks (src)
- Root
package.json build / build:watch --filter names
packages/react-components/vitest.config.mts aliases (../core, ../hooks, #sdk, #types)
.github/workflows/pgk-pr-new.yaml publish paths
packages/document doc content (file names unchanged)
pnpm-lock.yaml regeneration
Notes
- These packages are unpublished (v5,
1.0.0), so there are no external consumers to break.
- Targets the
v5.0.0 branch (the packages do not exist on main).
- Folder moves done via
git mv to preserve history.
Acceptance
pnpm build and pnpm test pass across all packages.
pnpm install --frozen-lockfile remains consistent.
Summary
Rename two v5 workspace packages — both the on-disk folder and the npm package name — for clearer, more descriptive naming.
packages/core(@commercelayer/core)packages/core-components(@commercelayer/core-components)packages/hooks(@commercelayer/hooks)packages/react-hooks-components(@commercelayer/react-hooks-components)Scope / affected areas
package.jsonnamefields for both packagesworkspace:*dependency declarations:react-hooks-components→core-components;react-components→ both@commercelayer/core/@commercelayer/hooksimport statements acrossreact-components(src + specs) andhooks(src)package.jsonbuild/build:watch--filternamespackages/react-components/vitest.config.mtsaliases (../core,../hooks,#sdk,#types).github/workflows/pgk-pr-new.yamlpublish pathspackages/documentdoc content (file names unchanged)pnpm-lock.yamlregenerationNotes
1.0.0), so there are no external consumers to break.v5.0.0branch (the packages do not exist onmain).git mvto preserve history.Acceptance
pnpm buildandpnpm testpass across all packages.pnpm install --frozen-lockfileremains consistent.