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

swc-plugin-use-prompt

v0.1.1

Published

A satirical attempt at making a `use prompt` directive for React and Next.js.

Downloads

149

Readme

"use prompt"

Add compile-time GenAI to any SWC-powered project!

function CoolButton() {
  "use prompt: a button that changes its background color when clicked";
}

export default function Home() {
  return <CoolButton />;
}

Installation

  1. Add the package as a dependency:

    $ pnpm add swc-plugin-use-prompt
  2. Add the plugin to your next.config.{ts,js} or .swcrc

    // next.config.js
    const nextConfig = {
      experimental: {
        swcPlugins: [["swc-plugin-use-prompt", {}]],
      },
    };

    or

    // .swcrc
    {
      "jsc": {
        "experimental": {
          "plugins": [["swc-plugin-use-prompt", {}]],
        },
      },
    }
  3. Run pnpm use-prompt alongside your regular build step!

    By default, this will watch your app and src directories for JS and TS files, but you can change this using the -p option.

Check out the Next.js example to see it in action.

Motivation

Inspired by the new "use cache" directive and relentless improvements in generative AI, this project's existence felt necessary.

How It Works

Generation happens in two passes: the CLI script and the SWC plugin.

The use-prompt CLI script uses @swc/core to parse through source code and identify all "use prompt:" directives. It extracts the prompts and calls OpenAI's API to generate code snippets, which are then saved in a cache file.

At compile time, the SWC plugin reads from this cache file and modifies the AST to insert the generated code before compilation is complete. There is some additional complexity around dealing with package import naming clashes, which is handled by substituting unique names for all imports required by a generated function / component.

Ideally, codegen would happen in a single pass. However, the SWC plugin runs in a WASM/WASI sandbox that doesn't have access to the network, so it's not possible to call remote APIs directly. This may be changed in the future though, since the SWC plugin API is very experimental.