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

cextup

v0.0.1

Published

A tool to make Chrome extension development less painful

Downloads

10

Readme

CExtUp

Chrome extension development can be painful. CExtUp is a CLI tool that aims to alleviate some of that pain, without doing too much. It provides a solid foundation for your projects, including a build system, a development server, and a basic project structure, but leaves the rest up to you.

CExtUp uses Bun—a modern JavaScript runtime, bundler, and package manager—instead of Node.js for its build system and server. It is also pre-configured to use Vercel Serverless Edge Functions, but should work with other serverless platforms as well.

Features

  • Project Setup: CExtUp automatically generates a new Chrome extension project with a basic structure and all the necessary files.
  • Bun Integration: We use Bun for its build system and server, providing an incredibly fast and efficient development experience.
  • TypeScript Support: Out-of-the-box support for TS, giving you more confidence in your code.
  • Edge Functions: CExtUp is set up to use Vercel Serverless Edge Functions, providing a scalable and efficient way to handle server-side logic. This is optional and can be removed if not needed. These live in the api/ directory.

Getting Started

To use CExtUp, run the following command:

bunx cextup
# or
npx cextup

This will prompt you for the name of your new extension and create a new directory with that name, containing all the necessary files for your new Chrome extension.

Project Structure

The generated project includes the following directories:

  • src/: source files for your Chrome extension, including background scripts, content scripts, and the manifest file
  • types/: TypeScript type definitions
  • api/: serverless functions for your extension (if applicable)
  • scripts/: scripts for building and serving your extension during development

When you run bun start, the extension/ directory will be created, containing the built extension. This directory is ignored by Git.

Development

First, make sure you have Bun installed:

curl -fsSL https://bun.sh/install | bash

To start developing your Chrome extension, navigate to the project directory and install the necessary dependencies:

cd your-extension-name
bun i

Then, start the development server and watch for changes:

bun start

If you want to build the extension without starting the development server, you can run:

bun ./scripts/build.ts

Note that while it is possible to use vercel dev to run the development server, it is much slower than using Bun, so we recommend using bun start instead.

Loading the Extension in Chrome

To load your extension in Chrome, navigate to chrome://extensions in your browser and click Load unpacked. Select the dist directory in your project. Note that you must have Developer Mode enabled in order to load unpacked extensions.

After making changes to your code, you will need to reload the extension by clicking the Update button in chrome://extensions.

Contributing

Contributions to CExtUp are welcome! Please create an issue or submit a pull request.

License

CExtUp is licensed under the MIT License. See the LICENSE file for more information.