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 🙏

© 2026 – Pkg Stats / Ryan Hefner

vite-plugin-pyths

v0.2.1

Published

Vite plugin for PythScribe — compile .ps and .psc files to JavaScript with Fast Refresh

Readme

vite-plugin-pyths

Vite plugin for PythScribe — compile .ps (Python) files to JavaScript on the fly.

Install

npm install -D vite-plugin-pyths

You also need the pyths CLI on PATH or built locally. The plugin auto-detects target/{debug,release}/pyths[.exe] and falls back to pyths on PATH.

Usage

// vite.config.js
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import pyths from "vite-plugin-pyths";

export default defineConfig({
  plugins: [pyths(), react()],
});

Now .ps files are first-class — import them anywhere a .js/.tsx file would be imported.

# src/Counter.ps
from pyths.react import component, use_state

@component
def Counter():
    count, set_count = use_state(0)
    return div()(
        h2()("Count: ", count),
        button(on_click=lambda: set_count(count + 1))("Increment")
    )
// src/App.jsx
import { Counter } from "./Counter.ps";
export default function App() { return <Counter />; }

Options

pyths({
  pythsBin: "/path/to/pyths",   // default: auto-detect
})

| Option | Default | Purpose | |---|---|---| | pythsBin | auto-detected | Absolute path to the pyths binary. Auto-detection probes target/{debug,release}/pyths[.exe], then pyths on PATH. |

How it works

  1. Vite's transform hook fires for every .ps import.
  2. The plugin shells out to pyths compile <file> --sourcemap.
  3. The resulting .js and .js.map are read, returned to Vite, and the temp files are deleted.
  4. Vite handles the resulting JS like any other module — bundling, HMR, source-map serving for DevTools.

HMR

.ps edits trigger a full reload. Component-level HMR (preserving state across edits) isn't currently supported — would require integrating with React Refresh after compilation.

Source maps

Enabled by default. Browser DevTools "Sources" panel shows the original .ps file; breakpoints and stack traces map back to it.

Performance

  • First compile: ~5–20 ms per file (Node startup + Rust toolchain).
  • Warm rebuilds (incremental cache hit): sub-millisecond.
  • Bundle overhead from pyths-runtime: ~3 KB gzipped.

Caveats

  • The plugin invokes the CLI per file. For projects with hundreds of .ps files, this becomes O(N · Node startup) — acceptable but not free. A future version may use the in-process Rust API.
  • Type-checking (pyths check) is a separate command — run it in CI or via your IDE's Python tooling.

License

MIT.