Skip to content

chore: rename core → core-components and hooks → react-hooks-components #801

Description

@acasazza

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-componentscore-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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions