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

@kendordev/vite

v0.1.0

Published

Vite plugin that makes a dev server reachable + HMR-correct through the Kendor sandbox reverse proxy. No-op off-platform, so it is safe to commit to any repo.

Readme

@kendor/vite

A tiny Vite plugin that makes a dev server reachable and HMR-correct through the Kendor sandbox reverse proxy — and does nothing anywhere else, so it is safe to commit to any repository.

npm install -D @kendor/vite
// vite.config.js
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import kendor from '@kendor/vite'

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

What it does

When your project runs inside a Kendor sandbox, the platform serves your dev server behind a per-session reverse proxy and injects one environment variable, KENDOR_VITE_ORIGIN, holding the dev server's own public origin. From it the plugin sets, only when that env is present:

  • server.host = true — bind all interfaces so the proxy can reach it.
  • server.allowedHosts = true — accept the proxied *.preview.<domain> Host (Vite 5+ blocks unknown Hosts).
  • server.origin + server.hmr — point asset URLs and the HMR WebSocket at the public origin, so assets resolve and hot-reload connects back through the proxy instead of to localhost.

Off-platform the env is absent and the plugin returns nothing — npm run dev behaves exactly as it would without it. This single plugin covers both plain Vite SPAs (it serves the page itself) and split-origin setups like Laravel or Rails, where Vite is a separate asset server on its own subdomain; the platform injects the right origin for each.

Laravel

Add it alongside laravel-vite-plugin — no other changes:

import { defineConfig } from 'vite'
import laravel from 'laravel-vite-plugin'
import kendor from '@kendor/vite'

export default defineConfig({
  plugins: [
    laravel({ input: ['resources/css/app.css', 'resources/js/app.js'], refresh: true }),
    kendor(),
  ],
})