nice-registry / ghub.io

🤸‍♀️ Redirect to an npm package's repository page

ghub.io

Redirect to an npm package's repository page, like ghub.io/express

Features

🌏 Supports GitHub, Gitlab, BitBucket, and others.

🚀 Stateless design using all-the-package-repos

🔒 HTTPS support

🌴 Always fresh with Dependabot

👫 Shared ownership in a GitHub org

🙌 Open Open Source contribution model

Web Usage

Visit ghub.io/<package-name> in your browser and you'll be taken to that package's repository page on GitHub or elsewhere. If the package has no specified repo you'll be redirected to npmjs.com.

Examples:

• ghub.io/electron (GitHub)
• ghub.io/jsonschema-extra (GitLab)
• ghub.io/pickles (BitBucket)
• ghub.io/some-nonexistent-package (npm)

CLI Usage

ghub is also available as a command-line tool which accepts one or many package names and opens their GitHub repos in your web browser:

npm i -g ghub
ghub choo chai chalk

The CLI can also read from newline-delimited standard input.

To open a repo tab for every dependency in a local package.json file:

npm i -g ghub json
cat package.json | json dependencies | json -ka | ghub

or every devDependency:

npm i -g ghub json
cat package.json | json devDependencies | json -ka | ghub

Pair ghub with the depnames CLI to open repo pages for all the dependencies of a given package:

npm i -g ghub depnames
depnames chokidar | ghub

View the top ten most-dependend-on packages whose names start with level:

npm i -g ghub all-the-package-names
all-the-package-names | egrep '^level' | head -n 10 | ghub

Repository

github.com/nice-registry/ghub.io

License

MIT

See Also

gem.wtf - a similar service, but for ruby gems

ghub.io's Issues

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Automatically deploy merged PRs to production

I see this is already hooked up in Heroku:

But maybe it stopped working because the app was on an old Heroku Stack. I've updated it to Heroku Cedar 24 (or whatever it's called), so maybe we're unblocked here. Let's see..

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

support monorepos / repository.directory

Currently, to support that we need to pass a full location link to package (e.g. https://github.com/user/repo/packages/foobar to the repository field, which isn't recommended in general.

There's also another reason for me to use the repository field that way, and it's because npm's package page doesn't respect repository.directory too (the "repository" link).

The only left possible workaround is to put it on the homepage but if you want to have a website there it's not an option.

For this purpose, we can instead use package-json or such package, to get the current package.json for a package.

Set up Greenkeeper

all-the-package-repos now updates itself daily. One way we can keep ghub's repo list up to date is by setting up @Greenkeeper, which will open PRs automatically when dependencies are updated.

support scoped modules

They make work already. In either case let's add some tests for @scoped/modules

Auto-accept Dependabot updates to the all-the-package-repos package

See #892 (comment)

Could also just change npm start to do npm i all-the-package-repos && node server.js or something. That would work, since Heroku apps restart every 24 hours. 🤷🏼

An in-range update of nodemon is breaking the build 🚨

The devDependency nodemon was updated from 1.18.5 to 1.18.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nodemon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v1.18.6

1.18.6 (2018-11-05)

Bug Fixes

• restart on change for non-default signals (#1409) (#1430) (521eb1e)

Commits

The new version differs by 1 commits.

• 521eb1e fix: restart on change for non-default signals (#1409) (#1430)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Open current repo

Good evening!

Just came across this repo, and I find it extremely cool 💯

How about adding the option to open the current project (if any)? One can obviously type ghub <name_of_repo>, but something like ghub current would be cool I guess 😄

Just an idea. Let me know if I can help with that in some way (some guidance would be nice).

Thanks!

Doesn't work for `@react-three/cannon`

For example, http://ghub.io/@react-three/cannon should redirect to the repository page., but it doesn't.

Also, I can see in packages.json this line:

"@react-three/cannon": "https://github.com/pmndrs/use-cannon"

But why then the link above doesn't redirect to the repository page?

migration plan

This is a followup to juliangruber/ghub.io#17

• invite @juliangruber and @rvagg to @nice-registry org (visit https://github.com/nice-registry to accept the invitation.)
• rename nice-registry/package.land repo to nice-registry/ghub.io
• update the readme: #9
• retire the old juliangruber/ghub.io with a notice in the README: juliangruber/ghub.io#28
• reimplement the CLI functionality function of the ghub module: #12
• point ghub.io DNS to Heroku: #14
• npm owner add zeke ghub (@juliangruber)
• set up semantic-release to autopublish ghub changes to npm

Point DNS at Heroku

@juliangruber I've added the domains on the Heroku app. I think all that's needed now is DNS:

ghub.io.herokudns.com
www.ghub.io.herokudns.com

async-to-genify is wrong

https://ghub.io/async-to-genify Redirects to https://www.npmjs.com/package/async-to-genify, whereas there is a repo https://github.com/goto-bus-stop/async-to-genify

Test the CLI

A CLI was implemented in #12 but I fast-tracked it without tests. Would be good to go back and get some coverage on that. See #12 (comment) for implementation ideas.

An in-range update of supertest is breaking the build 🚨

The devDependency supertest was updated from 3.3.0 to 3.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

supertest is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v3.4.0

• PR-532 - Packages updated, pipeline more explicit, documentation updated (thanks @rimiti)
• PR-517 - Documentation updated (thanks @oprogramador)
• PR-513 - Use more robust Array instance check (thanks @rubendg)

Commits

The new version differs by 14 commits.

• 5640ac9 3.4.0
• 60f8a9e Merge pull request #532 from visionmedia/v3.4.0
• 43bfae1 doc(History.md) changelog updated
• fc1568d doc(README.md) cookie example added
• 3192d96 chore(package-lock.json) file updated
• b3d271f chore(package.json) blocks reorganized, nock removed
• aeae0f3 chore(.travis.yml) pipeline more explicit
• 53feddc chore(test/supertest.js) obscure test removed
• 50c59d6 Merge pull request #519 from oprogramador/patch-3
• 6ca3897 Merge pull request #517 from oprogramador/patch-2
• 0146d81 auth info in README
• d853b37 fix typo in README
• 8158979 Merge pull request #513 from rubendg/use-isarray
• 550613b Use more robust Array instance check

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

support deep URLs

See https://github.com/juliangruber/ghub.io/blob/f5dffef663588cb0e58e9897553a1f786f808762/test/deep-urls.js

Funny redirects

Since repos[name] is being used, something funny happens if we open urls like:

/__defineGetter__
--> https://www.npmjs.com/package/function%20__defineGetter__()%20%7B%20[native%20code]%20%7D

Because repos.__defineGetter__ is a native function coming from the Object prototype.

I'm not even sure if we need to address this, but just in case. 😁

https://github.com/nice-registry/package.land/blob/f4cd43fde4c51b38833316f2f5eea0b994a0117e/server.js#L10-L14

Outdated information

See:

• http://ghub.io/memoize
• http://ghub.io/satori

Should open repos from Sondra Sorhus and Vercel respectively, but point to their original repos.

Also a package I published last week does not open GitHub at all:

• http://ghub.io/proper-event

The automated release is failing 🚨

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from 15.12.3 to 15.12.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v15.12.4

15.12.4 (2018-11-30)

Bug Fixes

• remove unnecessary branch parameter from push function (ffe1062)

Commits

The new version differs by 1 commits.

• ffe1062 fix: remove unnecessary branch parameter from push function

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Work not only for npm, but everything

See this new grassroot initiative https://github.com/package-url/purl-spec/