fix: reconnect package to repository after account transfer

[Copilot]

After transferring the repo to an org and back, the repository metadata in package.json fell out of sync — missing bugs/homepage fields and using incorrect URL casing.

Changes

• repository.url: corrected casing coldbydefault → ColdByDefault
• bugs: added field pointing to /issues
• homepage: added field pointing to #readme

"repository": {
  "type": "git",
  "url": "git+https://github.com/ColdByDefault/next-seo-lite.git"
},
"bugs": {
  "url": "https://github.com/ColdByDefault/next-seo-lite/issues"
},
"homepage": "https://github.com/ColdByDefault/next-seo-lite#readme"

Version and all functional config left untouched. A npm version patch && npm publish after merge will push the updated metadata to the registry.

Original prompt

Context

The repository ColdByDefault/next-seo-lite was transferred to an organization and then back to the personal account. The package needs to be reconnected to the repository by updating repository metadata in package.json.

The user reported they cannot merge the previous PR attempt.

Task

Update the package.json file to reconnect the package to this repository:

1. Locate package.json in the repository root
2. Update the repository field:

   "repository": {
     "type": "git",
     "url": "git+https://github.com/ColdByDefault/next-seo-lite.git"
   }

3. Update or add the bugs field:

   "bugs": {
     "url": "https://github.com/ColdByDefault/next-seo-lite/issues"
   }

4. Update or add the homepage field:

   "homepage": "https://github.com/ColdByDefault/next-seo-lite#readme"

5. Verify the package name - ensure it matches the intended scope (if using a scope like @coldbydefault/next-seo-lite, keep it consistent)
6. Check publishConfig if present - ensure it's correctly set for the target registry
7. Do NOT modify the version number

Expected Outcome

• All repository URLs in package.json point to ColdByDefault/next-seo-lite
• The package is ready to be republished to establish the connection
• The changes should be minimal and focused only on repository metadata

Notes

• Focus only on fixing the repository connection metadata
• Preserve all other package configuration
• This is a simple metadata update that should not affect functionality

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: how can i connect my packages to repo

Assistant: To connect your packages to your GitHub repo (ColdByDefault/next-seo-lite), you usually mean one of these:

1. Publish your package(s) to a registry (npm or GitHub Packages) and link them to the repo
2. Develop multiple packages inside the same repo (a monorepo/workspaces)
3. Depend on a package directly from GitHub (git URL)
4. Attach an already-published package to this repo in GitHub’s “Packages” tab

Tell me which one you want; meanwhile here are the main ways:

---

1) Publish to npm and link it to the GitHub repo (most common)

In your package’s package.json, set the repository fields:

{
  "name": "@coldbydefault/next-seo-lite",
  "version": "1.0.0",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/ColdByDefault/next-seo-lite.git"
  },
  "bugs": {
    "url": "https://github.com/ColdByDefault/next-seo-lite/issues"
  },
  "homepage": "https://github.com/ColdByDefault/next-seo-lite#readme"
}

Then publish:

• If it’s public:
  • npm login
  • npm publish --access public (needed for scoped public packages)

After publish, npm will show the GitHub link (repo/homepage), and GitHub can also show the package depending on how you publish/associate it.

---

2) Use GitHub Packages (publish package to GitHub and connect it to the repo)

This is common for private packages, or if you want everything on GitHub.

High-level steps:

• Create/update .npmrc to point your scope at GitHub’s registry
• Set publishConfig in package.json
• Authenticate with a GitHub token that has package permissions
• Publish with npm publish

If you tell me whether your package is npm (JavaScript/TypeScript) and whether it should be public or private, I’ll give you the exact .npmrc, package.json, and commands.

---

3) Make a monorepo (multiple packages inside the same repo)

If by “connect my packages” you mean “I have multiple local packages and want them in this repo”:

Use npm workspaces (or pnpm/yarn). Example structure:

• package.json (root)
• packages/pkg-a/package.json
• packages/pkg-b/package.json

Root package.json:

{
  "private": true,
  "workspaces": ["packages/*"]
}

Then you can import between packages and publish them independently (or together with a tool like changesets).

---

4) Install a package directly from the GitHub repo (no registry publish)

This is quick but less ideal for public consumption:

npm i github:ColdByDefault/next-seo-lite
# or with a branch/tag
npm i github:ColdByDefault/next-seo-lite#main

This “connects” consumers to your repo as the source of the dependency.

---

Quick questions so I can give you the exact steps

1. Are your packages JavaScript/TypeScript (npm), or something else (Python, Rust, etc.)?
2. Do you want to publish to npm or GitHub Packages?
3. Is the package public or private?
4. Do you have one package in the repo or multiple packages (monorepo)?

User: ok it was registered, but i ttansfered to my organization then transfer it back to my account.

Assistant: If the package was already registered (published) and you transferred the repo to an organization and then back to your personal account, the “c...

This pull request was created from Copilot chat.