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-pagefiles

v0.4.2

Published

Vite plugin to statically extract metadata from component files and generate client-side route declarations

Readme

vite-plugin-pagefiles

Vite plugin to statically extract metadata from React component files and generate client-side route declarations.

⚠️ Experimental

This plugin is pre-release, and its API is not stable. Use at your own risk. If you have feedback and/or bugs along the way, feel free to open an issue.

The plugin also currently only supports React applications. If you're familiar with other UI libraries, especially Vue, I'd be happy to help write support code.

How does it work?

This plugin allows you to write "pagefiles". A pagefile is a file that fully define a single route in your application. Here's a very basic example:

// Home.page.tsx
export const Meta = () => ({
  path: "/",
});

export default function Home() {
  return (
    <div>
      <h1>Home</h1>
      <p>Welcome to the homepage</p>
    </div>
  );
}

The file has two exports: Meta and default.

Meta is a function that defines metadata about the route that is made available at build-time. The only property in the object returned by this function that matters to the plugin is path, which is used to generate the route declaration, but you may add additional properties to handle as you wish.

Similar to other file-based routing solutions, the default export is used as the page component.

Why?

File-based routing solutions are great because they eliminate a lot of boilerplate involved in adding routes to your application. However, they force you to organize your code based on your URL organization, and they tend to incur high levels of nesting. This can make it harder to maintain a complex application.

Pagefiles is an alternative to file-based routing that still satisfies the story around convenience. But by pushing the route metadata into the route's file itself, you are free to make your own decisions about how you organize your code.

Getting Started

NPM

The plugin is published on npm as vite-plugin-pagefiles.

npm install -D vite-plugin-pagefiles

Vite config

// vite.config.ts
import { defineConfig } from 'vite';
import pagefiles from 'vite-plugin-pagefiles'

export default defineConfig({
  plugins: [
    // ...
    pagefiles(),
  ],
});

Use the generated routes in your App

import React, { Suspense } from "react";
import { BrowserRouter, useRoutes } from "react-router-dom";
import routes from "virtual:pagefiles";

function AppRoutes() {
  return <Suspense fallback={<div>Loading</div>}>{useRoutes(routes)}</Suspense>;
}

export default function App() {
  return (
    <BrowserRouter>
      <AppRoutes />
    </BrowserRouter>
  );
}

By default, the plugin imports pagefiles asynchronously using React.lazy(() => ...) to take advantage of bundle splitting. This means it's necessary to wrap the call to useRoutes in a Suspense block. This behavior is customizable.

Create a "pagefile"

By default, the plugin uses the glob src/**/*.page.tsx to discover pagefiles in your project.

Here's an example pagefile:

import type { PagefileMetaFn } from "vite-plugin-pagefiles";

export const Meta: PagefileMetaFn = () => ({
  path: "/",
});

export default function Home() {
  return (
    <div>
      <h1>Home</h1>
      <p>Welcome to the homepage</p>
    </div>
  );
}

Acknowledgements

This plugin is based on vite-plugin-pages and borrows heavily from its design. Thank you, @hannoeru and the other folks that have contributed to that project!