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

chrome-extensions-reloader

v1.1.1

Published

Automatically reload unpackaged chrome extensions on file change

Downloads

3

Readme

chrome-extensions-reloader

So, you're developping a chrome extension ? I bet you're doing with this pattern about 3.141e+42 a day:

  1. Make a change in your code
  2. Go to chrome://extensions
  3. Find your unpacked extension
  4. Click Reload
  5. Go to your extension and inspect your change, debug stuff ect
  6. Repeat

So, what if you could do this:

  1. Make a change in your code
  2. Go to your extension and inspect your change, debug stuff ect
  3. Repeat

image

How I install this awesome stuff ?

First, you should know that i've only tested using OSX but it should also work on Linux. However i'm not brave enought to test on Windows.

Requirements

  1. Install chrome-cli

    This is script use the awesome chrome-cli tool, since this CLI tool is a binary and platform dependant, you should install it before using this script.

  2. Install chrome-extensions-reloader, you may need sudo

    npm install -g chrome-extensions-reloader
  3. Open a tab in chrome to chrome://extensions-frame (yes, extensions-frame, not extensions)

Usage:

As a watcher:

chrome-extensions-reloader can watch a folder and reload the extension each time a change happen in this folder.

Go to your project root directoy:

$ cd my-awesome-chrome-extensions
$ chrome-extensions-reloader
>> SUCCESS	 Reloaded extensions (in tab 818)
>> SUCCESS	 Reloaded extensions (in tab 818)
[...]

As a sublime-text build system

You may find that watching a folder is very slow and that's true, blame fs.watch. That's why with a little of Sublime Text magic you can reload the extension just by pressing ctrl+s

  1. In Sublime Text create a new Build System: Tools > Build System > New Build System...

  2. Add this to the Build System file (example here)

    {
      "shell_cmd": "chrome-extensions-reloader --single-run"
    }
    
  3. There you go, each time you press ctrl+b it will reload the extension

You may want to install SublimeOnSaveBuild plugin to run the build script each time you press ctrl+s

FAQ

  1. What does this thing do under the hood ?

    This script simply inject a dumb javascript snippet which trigger a Click() on every Reload links in the chrome://extensions tab. That's why this tab should be open.

  2. Does it reload every extensions ?

    This script reload every unpackaged extensions

  3. Why is this repository name is too long ?

    Because letters make words and sometime there is too much letters