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

webpack-chrome-extension-launcher

v1.1.4

Published

Dedicated Chrome launcher for your extension development

Downloads

36

Readme

Chrome Extension Launcher

Jumptstart your Chrome extension development.

Why

Usually when developing a Chrome extension, you must first go to the chrome://extensions/ page, enable developer mode, load the unpacked extension, select its path, and finally open background page devtools.

This webpack plugin spares you all of those clicks. 💅

Get Started

Install Chrome Extension Launcher :

npm i -D webpack-chrome-extension-launcher
# or
yarn add -D webpack-chrome-extension-launcher

Add to your Webpack config :

const ChromeExtensionLauncher = require('webpack-chrome-extension-launcher')

module.exports = {
  // your webpack config
  mode: 'development'
  //...
  
  plugins: [new ChromeExtensionLauncher()],
}

🚀 A dedicated Chrome instance loaded exclusively with your unpacked extension will launch once after initial compilation (no need to worry about watch mode), with the following perks :

  • Developer mode enabled.
  • chrome://extensions/ as homepage.
  • Background page devtools opened on startup.
  • Webpack process killed on Chrome instance exit.

Options

  • autoDevtools: have Chrome devtools automatically opened in new tabs.
  • launchURL: start Chrome with a custom URL.
  • path: Chrome Extension Launcher looks for an unpacked extension in the output.path property of your webpack config, but you can specify your own path.
new ChromeExtensionLauncher({
  autoDevtools: true,
  launchURL: 'https://github.com',
  path: '/path/to/extension'
})

Production build

Chrome Extension Launcher is automatically disabled in mode: 'production'.

How about

Hot reloading

If you don't want to click on the reload button every time you make a change, use together with Chrome Extension Reloader from Rubens Pinheiro.

Better logging

If you want to centralize all your logs in the background page, use together with Web Extension Background Logger from me. 🙂