Skip to content

chore: add npm metadata links#191

Open
gshaowei6 wants to merge 1 commit into
larksuite:mainfrom
gshaowei6:chore/npm-metadata-links
Open

chore: add npm metadata links#191
gshaowei6 wants to merge 1 commit into
larksuite:mainfrom
gshaowei6:chore/npm-metadata-links

Conversation

@gshaowei6

Copy link
Copy Markdown

Summary

This updates the npm package metadata in package.json:

  • adds the GitHub repository metadata
  • replaces the non-standard top-level url field with standard bugs.url
  • keeps the existing homepage link

No runtime code, dependencies, build config, or generated files are changed.

Verification

  • node -e "const p=require('./package.json'); if (p.repository?.url !== 'https://github.com/larksuite/node-sdk.git' || p.bugs?.url !== 'https://github.com/larksuite/node-sdk/issues' || Object.prototype.hasOwnProperty.call(p,'url')) process.exit(1)"
  • git diff --cached --check
  • npm pack --dry-run --json --ignore-scripts
  • corepack yarn install --frozen-lockfile --ignore-scripts
  • corepack yarn build completed successfully on Windows; it prints existing TypeScript/Rollup warnings and a Windows rm warning, but exits 0.
  • WSL Ubuntu 26.04:
    • npm pkg get repository homepage bugs --json
    • npm pack --dry-run --json --ignore-scripts

I also tried corepack yarn test --runInBand; it did not complete within 5 minutes in my local Windows run, so I stopped the leftover Jest process. This change is limited to package metadata.

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants