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

kino

v1.0.0-alpha.6

Published

Remote

Downloads

5

Readme

Kino Build Status JavaScript Style Guide

A chrome extension to easily manipulate chrome pages from the comfort of your text editor or OS.

Usage

  1. Install kino npm i kino -g and run kino init to create the native messaging host
  2. Install the chrome plugin via the chrome web store
  3. Install an editor plugin like the vim plugin or the CLI via kino action directly

By default, there are actions defined for toggling video playback on youtube.com and egghead.io as an example. You can add other domains and define custom actions for them via the options page. Once this is done, you can trigger an action using the client to play the code for that action on an active chrome tab for the corresponding domain.

Here's a quick start video to help you get up and running:

Kino Quick Start

Todo

  • [x] spike extension -> native message host
  • [x] spike application -> native message host
  • [x] spike extension -> content script -> player controls (youtube)
  • [x] user defined commands
  • [x] Figure out a more universal away to do pathing for node in host

Niceties:

  • [ ] Page action that allows you to add a host/action from the current page
  • [ ] Local storage based logging for troubleshooting
  • [ ] Pass metadata though action messages?

Troubleshooting

There's currently not a great way to troubleshoot Kino issues without installing the extension unpacked. There are a few things you can do without going into Dev mode:

Common issues

  • have you installed kino globally and run kino init ?
  • Is node available at /usr/local/bin/node? If not, ln -s <path to node> /usr/local/bin/node and disable/enable the extension
    • alas, chrome cannot use /usr/bin/env node when launching the native extension host

Contributing

  1. Fork repo
  2. Clone down repo
  3. In chrome, go to tools > extensions
  4. Click "load unpacked extension"
  5. Navigate to the repository directory and load it
  6. Take note of the "id: " under the loaded extension and add it to the allowed_origins array in host/com.nicktomlin.kino.json
  7. Run ./bin/kino init to install the native messaging host
  8. Reload the extension

There is very light logging available via the background page:

  • Open the background page (or menu > "more tools" > "extensions" and click "background page")
  • Open the console
  • hit reload and see what error messages pop up
  • attempt to send a kino action kino action toggle and see if there is any logging