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

kubed

v0.0.3

Published

Low-level request wrapper for Kubernetes API

Downloads

6

Readme

Kubed

Build Status Coverage Status Dependency Status npm version

Simple Kubernetes API Client

This small module wraps request with enough to make lower-level Kubernetes API request. It does not attempt to cover all of the API endpoints covered in the API definition because it's changing too quickly for me to personally maintain it up to date. It does provide a sane starting point for anyone wanting to make calls from to the API from node through the proxy or from within a container.

Warning

Unstable work in progress. Currently designing, documenting and testing. This will probably not work for you yet.

Usage

npm i kubed

Defaults

If no options are passed, this will default to using the kubectl proxy's default values (ie: localhost:8080). If the environment variables: KUBERNETES_SERVICE_HOST and KUBERNETES_PORT_443_TCP_PORT are set, it is assumed that you are running within a Kubernetes-deployed container and defaults are changed accordingly.

const Kubed = require('kubed');
const client = new Kubed();
// client.get...

With Options

If no options are passd, this will default to using the kubectl proxy's default values (ie: localhost:8080). If the environment variables: KUBERNETES_SERVICE_HOST and KUBERNETES_PORT_443_TCP_PORT are set, it is assumed that you are running within a Kubernetes-deployed container and defaults are changed accordingly.

const Kubed = require('kubed');
const client = new Kubed({
  baseUrl: 'https://localhost:8080',
});
// or...
const client = new Kubed({
  token: `/path/to/token`,
  ca: `/path/to/ca.crt`,
});
// client.get...

Contributing

  • Fork the repo.
  • npm i
  • npm start to work on the library. This runs the tests continuously watching for changes but without test output (debug output instead).
  • Make your changes
  • npm t to run the tests with no debug output (tap output instead).
  • npm run cov to run coverage report.
  • npm run linter to run eslint.
  • Submit a PR.