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

@aboulbox/vite-plugin-rolling-release

v1.0.0

Published

A plugin to create a symlink to your custom build directory

Readme

⚡️ Vite Plugin Rolling Release npm license

A plugin to build viteJS app in a custom directory and then create a symlink at /dest/current pointing to your custom directory.

My usecase is the following :

  • I have a website build with Vite
  • My website is served by Caddy as a static site with file_server
  • When I update my website, if the build phase is long, Caddy could serve a mid-state site or completely crashed
  • My plugin allow me to build in a custom direct, then creating a symlink at dest/current, pointing to the new build directory once it's finish
  • This way, i'm 0️ down time.

Installation

npm install @aboulbox/vite-plugin-rolling-release

🔌 Usage

Add the plugin to your vite.config.js file.

import { defineConfig } from "vite";
import rollingrelease from "vite-plugin-rolling-release";

const buildDir = "dest/release_" + Date.now(); // Example
const outDir = import.meta.env.DEV ? "dist" : buildDir; // Don't need to change `outDir` for development but outDir must be the same as `buildDir` when building

export default defineConfig({
  plugins: [rollingrelease(buildDir)],
  outDir: outDir,
});

🧰 Options

buildDir

  • Type: string

  • Default: ''

    This is your build directory that dest/current will point to.

    ⚠️ buildDir must be relative to project root.

buildDir

  • Type: string

  • Default: ''

    This is your build directory that dest/current will point to.

    ⚠️ buildDir must be relative to project root.

buildDir

  • Type: string

  • Default: ''

    This is your build directory that dest/current will point to.

    ⚠️ buildDir must be relative to project root.

buildDir

  • Type: string

  • Default: ''

    This is your build directory that dest/current will point to.

    ⚠️ buildDir must be relative to project root.

💡 Ideas

  • [x] Add an option to change the default symlink location (dest/current for now)
  • [ ] Add an option to clean releases and a option keep: X where X is the number of releases to keep.
  • [ ] Add an option for rolling release names (release_<gitsha> || <timestamp> || <random>)

🛠️ Development

  • Install dependencies:
npm install
  • Build the library:
npm run build

License

MIT LICENSE