Skip to content

Rebrand Phase 1: Rename npm scope @phoenix-rooivalk/ → @nexamesh/ #777

@JustAGhosT

Description

@JustAGhosT

Context

NexaMesh rebrand. Customer-facing docs already updated. This issue covers the codebase-level npm scope rename.

Files to Update (11 package.json files)

  • package.json (root)
  • packages/types/package.json@phoenix-rooivalk/types@nexamesh/types
  • packages/ui/package.json@phoenix-rooivalk/ui@nexamesh/ui
  • packages/utils/package.json@phoenix-rooivalk/utils@nexamesh/utils
  • apps/marketing/package.json — dependency references
  • apps/docs/package.jsonphoenixrooivalk-docsnexamesh-docs + dependency refs
  • apps/docs/azure-functions/package.json — dependency references
  • apps/threat-simulator-desktop/package.json — description
  • e2e/package.json — dependency references
  • apps/marketing/tsconfig.json — path aliases
  • apps/marketing/vitest.config.ts — path aliases

Also update

  • All import statements referencing @phoenix-rooivalk/
  • pnpm-lock.yaml (regenerate via pnpm install)

Verification

  • pnpm install succeeds
  • pnpm build succeeds
  • pnpm test passes
  • All import paths resolve correctly

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions