use-bun-instead-of-node-vite-npm-pnpm

use-bun-instead-of-node-vite-npm-pnpm is a cursor rule for Cursor from pylarco/diff-apply. It costs 0 tokens per session (697 once invoked), scanned A, a copy of use-bun-instead-of-node-vite-npm-pnpm, MIT.

A set of coding rules that tells projects to use Bun, a JavaScript and TypeScript runtime and toolkit, instead of Node.js and common package tools.

In plain words
What is it for?
It is for running scripts and tests, installing packages, building files, and serving web applications with Bun.
Why use it?
It keeps commands, libraries, and runtime choices consistent around Bun rather than mixing several toolchains.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It is for running scripts and tests, installing packages, building files, and serving web applications with Bun.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pylarco/diff-apply/use-bun-instead-of-node-vite-npm-pnpm
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/pylarco/diff-apply

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for use-bun-instead-of-node-vite-npm-pnpm

README.md
[![agentmods](https://agentmods.dev/badge/rules/pylarco/diff-apply/use-bun-instead-of-node-vite-npm-pnpm/github.svg)](https://agentmods.dev/rules/pylarco/diff-apply/use-bun-instead-of-node-vite-npm-pnpm)
Your own site
<a href="https://agentmods.dev/rules/pylarco/diff-apply/use-bun-instead-of-node-vite-npm-pnpm"><img src="https://agentmods.dev/badge/rules/pylarco/diff-apply/use-bun-instead-of-node-vite-npm-pnpm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for use-bun-instead-of-node-vite-npm-pnpm

Your own site · 80×15
<a href="https://agentmods.dev/rules/pylarco/diff-apply/use-bun-instead-of-node-vite-npm-pnpm"><img src="https://agentmods.dev/badge/rules/pylarco/diff-apply/use-bun-instead-of-node-vite-npm-pnpm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00697
Opus 5 $0.00000 $0.00349
Sonnet 5 $0.00000 $0.00139
Haiku 4.5 $0.00000 $0.00070

Measured 7d ago against content hash 86c6d9c0f94c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

use-bun-instead-of-node-vite-npm-pnpm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

98% identical to use-bun-instead-of-node-vite-npm-pnpm — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Default to using Bun instead of Node.js.

  • Use bun <file> instead of node <file> or ts-node <file>
  • Use bun test instead of jest or vitest
  • Use bun build <file.html|file.ts|file.css> instead of webpack or esbuild
  • Use bun install instead of npm install or yarn install or pnpm install
  • Use bun run <script> instead of npm run <script> or yarn run <script> or pnpm run <script>
  • Bun automatically loads .env, so don't use dotenv.

APIs

  • Bun.serve() supports WebSockets, HTTPS, and routes. Don't use express.
  • bun:sqlite for SQLite. Don't use better-sqlite3.
  • Bun.redis for Redis. Don't use ioredis.
  • Bun.sql for Postgres. Don't use pg or postgres.js.
  • WebSocket is built-in. Don't use ws.
  • Prefer Bun.file over node:fs's readFile/writeFile
  • Bun.$ls instead of execa.

Frontend

Use HTML imports with Bun.serve(). Don't use vite. HTML imports fully support React, CSS, Tailwind.

Server:

import index from "./index.html"

Bun.serve({
  routes: {
    "/": index,
    "/api/users/:id": {
      GET: (req) => {
        return new Response(JSON.stringify({ id: req.params.id }));
      },
    },
  },
  // optional websocket support
  websocket: {
    open: (ws) => {
      ws.send("Hello, world!");
    },
    message: (ws, message) => {
      ws.send(message);
    },
    close: (ws) => {
      // handle close
    }
  },
  development: {
    hmr: true,
    console: true,
  }
})

HTML files can import .tsx, .jsx or .js files directly and Bun's bundler will transpile & bundle automatically. <link> tags can point to stylesheets and Bun's CSS bundler will bundle.

<html>
  <body>
    <h1>Hello, world!</h1>
    <script type="module" src="./frontend.tsx"></script>
  </body>
</html>

With the following frontend.tsx:

import React from "react";

// import .css files directly and it works
import './index.css';

import { createRoot } from "react-dom/client";

const root = createRoot(document.body);

export default function Frontend() {
  return <h1>Hello, world!</h1>;
}

root.render(<Frontend />);

Read the full file on GitHub · 100 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 100 lines · 0 tokens per session scan A 86c6d9c0f94c

Subscribe to this mod's changes

use-bun-instead-of-node-vite-npm-pnpm is a cursor rule published in the GitHub repository pylarco/diff-apply (10 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 697 tokens. A static security scan graded it A with 0 findings. It is 98% identical to use-bun-instead-of-node-vite-npm-pnpm, differing in 3 lines, and is treated as a copy.