Skip to content

Incorrect repository fields in package.json files across the monorepo #8249

@orien

Description

@orien

Problem

Several packages in this monorepo have incorrect repository and homepage fields in their package.json files. npmjs.com uses these fields to render the Repository and Homepage links on each package's page — so incorrect values send users to the wrong repo or a broken URL.

Specific issues found:

  1. Wrong URL prefix — root package.json and containers/node-bootstrap-container/package.json use git+https:// instead of https://
  2. Stale repo URL — all core/ packages still reference the old google-cloud-node-core.git repo instead of google-cloud-node.git, and their directory and homepage paths are missing the core/ prefix
  3. Wrong directory/homepage values in three packages:
    • google-cloud-beyondcorp-clientconnectorservices points to clientgateways
    • google-cloud-mediatranslation has a typo (media-translatation)
    • google-cloud-workflows points to google-cloud-workflows-executions
  4. String repository fields — 37 samples/ and other package.json files use the shorthand string form (e.g. "googleapis/nodejs-asset") pointing to old individual repos instead of a proper object pointing to the monorepo

Expected

All repository fields should be objects with:

  • type: "git"
  • url: "https://github.com/googleapis/google-cloud-node.git"
  • directory: the package's path within the monorepo

And homepage should point to https://github.com/googleapis/google-cloud-node/tree/main/<directory>.

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