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

@devwizard/vite-plugin-enumify

v0.1.3

Published

Vite plugin for Laravel Enumify - auto-sync PHP enums to TypeScript

Readme

@devwizard/vite-plugin-enumify

NPM GitHub

Vite plugin for Laravel Enumify — automatically sync PHP enums to TypeScript during development and builds.

Features

  • Runs php artisan enumify:sync --force --quiet before Vite compiles
  • Watches enum directories in dev mode (debounced)
  • Reads config/enumify.php to discover paths and watch config
  • Ignores changes inside the output directory to avoid infinite loops
  • Cross-platform: Windows/macOS/Linux

Package Links

  • NPM: https://www.npmjs.com/package/@devwizard/vite-plugin-enumify
  • Repository: https://github.com/devwizardhq/laravel-enumify
  • Composer (Laravel package): https://packagist.org/packages/devwizardhq/laravel-enumify

Installation

npm install @devwizard/vite-plugin-enumify --save-dev
# or
pnpm add -D @devwizard/vite-plugin-enumify
# or
yarn add -D @devwizard/vite-plugin-enumify

Package Manager Support

This plugin is package-manager agnostic and works with npm, pnpm, or yarn. The runtime behavior is identical regardless of how you install it.

Usage

Add the plugin to your vite.config.ts:

import { defineConfig } from "vite";
import laravel from "laravel-vite-plugin";
import enumify from "@devwizard/vite-plugin-enumify";

export default defineConfig({
  plugins: [
    enumify(),
    laravel({
      input: ["resources/js/app.ts"],
      refresh: true,
    }),
  ],
});

How It Works

  1. On Build Start: runs php artisan enumify:sync --force --quiet before Vite compiles TypeScript.
  2. Watch Mode: watches the enum paths from config/enumify.php and re-syncs on changes.
  3. Safe Output: ignores changes under the output directory to avoid re-trigger loops.

Options

enumify({
  // PHP binary path (default: "php")
  artisanBin: "php",

  // Path to the artisan file (default: "artisan")
  artisanFile: "artisan",

  // Command to run (default: "enumify:sync")
  syncCommand: "enumify:sync",

  // Working directory (default: process.cwd())
  cwd: process.cwd(),

  // Enable watch mode in development (default: runtime.watch from config/enumify.php)
  watch: true,

  // Additional environment variables
  env: {},
});

The plugin reads config/enumify.php to discover enum paths and output paths so it can watch the right files and avoid feedback loops.

Example

Given this PHP enum:

// app/Enums/OrderStatus.php
enum OrderStatus: string
{
    case PENDING = 'pending';
    case PROCESSING = 'processing';
    case SHIPPED = 'shipped';

    public function label(): string
    {
        return match ($this) {
            self::PENDING => 'Pending',
            self::PROCESSING => 'Processing',
            self::SHIPPED => 'Shipped',
        };
    }

    public function color(): string
    {
        return match ($this) {
            self::PENDING => 'yellow',
            self::PROCESSING => 'blue',
            self::SHIPPED => 'green',
        };
    }
}

The plugin generates:

// resources/js/enums/order-status.ts
export enum OrderStatus {
  Pending = "pending",
  Processing = "processing",
  Shipped = "shipped",
}

export type OrderStatusValue = `${OrderStatus}`;

export const OrderStatusLabels: Record<OrderStatus, string> = {
  [OrderStatus.Pending]: "Pending",
  [OrderStatus.Processing]: "Processing",
  [OrderStatus.Shipped]: "Shipped",
};

export const OrderStatusColors: Record<OrderStatus, string> = {
  [OrderStatus.Pending]: "yellow",
  [OrderStatus.Processing]: "blue",
  [OrderStatus.Shipped]: "green",
};

Git Workflow

  1. Create a feature branch from main
  2. Make changes with focused commits
  3. Run npm run build and npm run typecheck
  4. Open a PR and ensure CI passes

Release tip: tag releases after merging to main, then publish to NPM.

Requirements

  • Node.js >= 18.0.0
  • Vite >= 4.0.0 (including Vite 7)
  • PHP >= 8.2
  • Laravel Enumify package installed

License

MIT