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

ext-skeleton

v0.0.32

Published

`npx ext-skeleton <name>` or `npx ext-skeleton ./`

Downloads

2

Readme

Creating the Skeleton

npx ext-skeleton <name> or npx ext-skeleton ./

Modifying the skeleton

Install node modules and build the extension

  • terminal -> npm i
  • terminal -> npm run build:extension
  • Go To Chrome -> Manage Extensions -> Toggle Developer Mode -> Load Unpacked -> Select the dist folder

manifest.json

  • Change name
  • Change Version
  • Add your icon in the manifest
// ./public/manifest.json
...
"name": "<YOUR_EXTENSION_NAME>",
"version": "<YOUR_VERSION> usually you start from 0.0.1",
"description": "<DESCRIBE_YOUR_EXTENSION>",
...

Remove the tutorial page (if you need to keep the new tab page just modify)

  • Remove the components ./src/tutorialMain.tsx and ./src/components/tutorialPage folder
  • Remove the example component of the popup ./src/popup/components/ComponentExample.tsx
  • Update the ./vite.config.ts build
...
input: {
    main: 'index.html',
    // <tutorial: 'tutorial-page.html'> (remove this)
},
...

Or modify it if you would want to use this page as your new tab page.

Define the different components of your extension from the examples

  • Background script
  • Content script
  • Popup
  • Context menu
  • Storage
  • Ports
  • Inject script
  • Inject function

You can add or remove components as you please in order to define your strategy for the extension.

Because of modularity, you can just remove a specific module and it will not affect the rest of the extension.