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

roger-frank

v1.0.0

Published

[![Build Status](https://travis-ci.org/spinnaker/deck-kayenta.png?branch=master)](https://travis-ci.org/spinnaker/deck-kayenta)

Downloads

6

Readme

Spinnaker Canary UI

Build Status

Development

Make sure that node and yarn are installed on your machine. The minimum versions for each are listed in package.json.

To develop this module, run it as a Deck dependency using either yalc (recommended) or npm link.

yalc

Globally install yalc.

From the root of this repository, run

yalc publish

From the root of the main Deck repository, run

yalc add @spinnaker/kayenta
yarn start

As you make additional changes in this repository, run

yalc publish --push

npm link

From the root of this repository, run

npm link

From the root of the main Deck repository, run

npm link @spinnaker/kayenta

You should only have to run these commands once.

Next, run WATCH=true yarn lib at the root of this repository. In a separate terminal, run yarn start at the root of the main Deck repository.

Environment Variables

deck-kayenta uses feature and development flags. These are fully configurable within settings.js, but it is usually easier to pass the flags as environment variables.

These are good defaults:

REDUX_LOGGER=true \
API_HOST=http://localhost:8084 \
METRIC_STORE=stackdriver \
CANARY_STAGES_ENABLED=true \
TEMPLATES_ENABLED=true \
yarn start

Publishing @spinnaker/kayenta

This module is published as an NPM package.

  • Create a pull request that increments package.json's patch version - e.g., to 0.0.57.
  • Once the pull request has been merged, publish a release using the same tag as package.json's version, e.g., v0.0.57. @spinnaker/kayenta will be automatically published to NPM.

Once @spinnaker/kayenta has been published, it's likely that you'll want to update the main Deck repository: to do so, run yarn add @spinnaker/kayenta@latest in the main Deck repository, then open a pull request.

Testing

To run deck-kayenta's tests, run yarn test.

To run deck-kayenta's tests and generate a code coverage report, run yarn test-coverage. Open /coverage/html/index.html in a browser to view the HTML version of the report.