npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

code-repositories-api-common

v0.1.12

Published

This package offers a wrappers to GitLab/GitHub/BitBucket APIs.

Downloads

62

Readme

Code repositories API / common

This package offers a wrappers to GitLab/GitHub/BitBucket APIs.

The motivation for this package was to access hosted repositories and their issues, for them to be used in a project/time tracking app. Hence I wanted to have a common API to access those objects from these three major code hosting providers.

How it works?

This common package isn't standalone. By this I mean that it needs a companion package in order to work. The common package performs calls to APIs through GET or POST calls (so far). Because the tool is meant to be usable both from Node.js or from the browser, the actual requesting is left to the companion package, which we could call the request strategy package.

Currently there is one working companion package: code-repositories-api-node. Another is planned for use from the browser within Angular apps (code-repositories-api-angular).

TODO

  • Document
  • Test (underway, in separate package)
  • When setting token, also set scopes, so we can prevent using some methods if they are forbidden by scope.