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

bun-banner-plugin

v0.1.2

Published

Insert an arbitrary string at the beginning of generated content. Inspired by esbuild banner option.

Downloads

271

Readme

bun-banner-plugin

A small plugin to insert an arbitrary string at the beginning of generated content. Inspired by esbuild banner option.

Installation

bun add -D bun-banner-plugin

Usage

build.ts:

import { bannerPlugin } from "bun-banner-plugin";

await Bun.build({
  entrypoints: ["src/index.ts"],
  outdir: "dist",
  target: "node",
  minify: true,
  plugins: [
    bannerPlugin({
      // Add banners to json files
      jsonc: ["// This is a jsonc file", "// Hello, jsonc!"],

      // Add a shebang to the top of `.ts`, `.tsx`, `.js`, `.jsx` files
      "ts|tsx|js|jsx": "#!/usr/bin/env node",
    }),
  ],
});

Example

Suppose you have the following src/index.ts.

console.log("Hello, world!");

Now, using the build.ts I wrote in Usage, run bun run build.ts, the following will be output:

#!/usr/bin/env node
console.log("Hello, world!");

Options

  • The key is a regular expression that matches the file extension.
    • The given key is interpreted as a regular expression, so you need to escape special characters.
    • For example:
      • If the key is json, it will interpreted as /.(json)$/. It will match .json files.
      • If the key is ts|tsx|js|jsx, it will iterpreted as /.(ts|tsx|js|jsx)$/. It will match .ts, .tsx, .js, .jsx files.
  • The value is the string to be inserted at the beginning of the file.
    • If the value is an array, the strings in the array will be joined with a newline character.

    • If the value is a string, it will be inserted as is.

    • For example, If the value is ["// This is a jsonc file", "// Hello, jsonc!"], it will be inserted as follows:

      // This is a jsonc file
      // Hello, jsonc!
      {
        "foo": "bar",
      }

Development

Commands

| Command | Description | | ----------------------------- | ------------------------------------------------- | | bun install | Install dependencies | | bun run build | Build the project | | bun run test | Run tests with watch mode | | bun run check | Lint and format | | npm publish --dry-run | Check locally for products to be published to npm | | npm publish --access public | Publish to npm |

Publish

  1. Update version in package.json
  2. commit with tag vX.X.X
  3. push to GitHub