Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

kino

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

kino

Remote

  • 1.0.0-alpha.6
  • latest
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

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

  • spike extension -> native message host
  • spike application -> native message host
  • spike extension -> content script -> player controls (youtube)
  • user defined commands
  • 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

FAQs

Package last updated on 10 Nov 2017

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc