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

@openelement/adapter-vite

v0.41.0-alpha.1

Published

openElement build orchestration for Vite.

Downloads

51

Readme

@openelement/adapter-vite

openElement build orchestration for Vite.

v0.39 surface: advanced Framework infrastructure. First-run apps should use @openelement/app/vite or generated @openelement/create tasks instead of importing this package directly.

This package scans routes and islands, generates virtual entries, builds client island chunks, runs SSG, and writes post-processed HTML. It is build-time infrastructure; runtime primitives live in @openelement/core.

Install

npm install @openelement/adapter-vite

Usage

import { createOpenPlugin } from '@openelement/adapter-vite/plugin';
import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [
    createOpenPlugin({
      routesDir: 'app/routes',
      islandsDir: 'app/islands',
      componentsDir: 'app/components',
      packageIslands: ['@openelement/ui'],
    }),
  ],
});

Most applications should use openElement() from @openelement/app/vite instead; it combines the core adapter, content pipeline, and i18n with one shared build context.

Main Options

| Option | Default | Purpose | | ---------------- | ------------------ | ----------------------------------------------- | | routesDir | 'app/routes' | Page routes, API routes, renderers, middleware. | | islandsDir | 'app/islands' | Local Custom Elements for client upgrade. | | componentsDir | 'app/components' | Shared server-rendered components. | | packageIslands | [] | Packages exporting an islands metadata array. | | html | {} | Document metadata. | | inject | none | Structured stylesheet/script/head injection. | | middleware | none | Hono middleware configuration. | | pwa | none | PWA metadata and assets. |

SSG Pipeline

Phase 1: route, API, middleware, and island scan
Phase 2: client island entry and browser chunks
Phase 3: SSR bundle, Hono toSSG(), HTML post-processing

Build Utilities

import {
  buildIslandChunkMap,
  extractCustomElementTags,
  generateIslandManifests,
  injectClientScript,
  injectCspMeta,
  injectDsdPolyfill,
  scanClientBuild,
  scanSSGOutput,
  writeIslandManifests,
} from '@openelement/adapter-vite';

Registry Boundary

packageIslands currently scans packages that export islands. It should not be treated as a complete marketplace or registry protocol. Future open add behavior must first validate a CEM-compatible manifest, generate a dry-run diff, and only then update config and generated registration.

License

MIT