chore: include GitHub link in package.json#5
Merged
RomainLanz merged 1 commit intoboringnode:mainfrom Mar 3, 2026
Merged
Conversation
Member
|
Oh yes, totally forgot that! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the GitHub repository link inside
package.json.This allows to have the link to the repository available on the npm package page: https://www.npmjs.com/package/@boringnode/queue
I find it painful to not have it, when I'm on the npm page (even if arguably we can easily find the repostory).
Could also open similar PRs, to all @boringnode packages.