refactor: replace the parse-link-header dev dependency

[therealharshit]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: na
• task: lint_package_json status: passed
• task: lint_repl_help status: na
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: na
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

Description

What is the purpose of this pull request?

This pull request:

• Remove the external parse-link-header dependency from the root development dependency and replace its only in-repo usage with a local parser in _tools/github/get.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• #{{TODO: add related issue number}}

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[therealharshit]

The dependency parse-link-header is also listed in the npm configuration file at ets/npm/deps.txt, which I did not remove. Please let me know if it is required from my end.

[kgryte]

I suggest turning the link header logic into its own package: @stdlib/_tools/github/parse-link-header, with its own docs, examples, tests. This way the logic can be reused across all tools packages needing to support pagination on GitHub.

[therealharshit]

This way the logic can be reused across all tools packages needing to support pagination on GitHub.

@kgryte Thanks for the review.
I chose this minimal approach because @stdlib/_tools/github/get/lib/resolve.js is currently the only consumer of parse-link-header.

[therealharshit]

I suggest turning the link header logic into its own package: @stdlib/_tools/github/parse-link-header, with its own docs, examples, tests.

I think the @stdlib/utils/parse-link-header namespace would be more appropriate for the parse-link-header package. Let me know what you think? so I can procees with the changes.