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-api-auto-import

v0.1.3

Published

Auto-import API generator for Vite

Readme

vite-plugin-api-auto-import

Auto-generate a typed API import module and inject it on-demand into your source files. Works with Vite7 and Vue 2.x/3.x.

Install

pnpm add -D vite-plugin-api-auto-import
# or npm i -D vite-plugin-api-auto-import / yarn add -D vite-plugin-api-auto-import

Usage

vite.config.ts (recommended static import)

import { defineConfig } from 'vite'
import autoApi from 'vite-plugin-api-auto-import'

export default defineConfig({
  plugins: [
    autoApi({
      name: '$apis',           // global symbol used in your code
      dir: 'api',              // directory with your API modules
      constApiData: '$apiData',
      outFile: 'index.ts',     // generated file name inside `dir`
      include: [               // files to inject import into when they reference `name`
        /\.[tj]sx?$/,
        /\.vue$/, /\.vue\?vue/,
        /\.md$/,
      ],
      // optional
      resolvers: [
        // { from: '../data', resolve(mod) { return { ccc: mod.ccc } } }
      ],
      // create a Vite alias pointing to your API root automatically
      autoResolveAliasName: true,
      // or set a custom alias explicitly
      // resolveAliasName: '@apis',
      allExport: false,
      import: true, // true | false | 'namedExport'
    })
  ]
})

CommonJS config (vite.config.cjs/js) can use dynamic import

const { defineConfig } = require('vite')
module.exports = defineConfig(async () => {
  const { default: autoApi } = await import('vite-plugin-api-auto-import')
  return { plugins: [autoApi()] }
})

Then reference $apis in your app code and the plugin injects a single import to the generated module.

Compatibility

  • Node >= 14.18 (Node 16+ recommended)
  • Vite 2 → 6

Changelog

0.1.2

  • Fix: generated identifiers strip file extensions correctly and sanitize names. For example security/encrypt.tssecurity_encrypt_import (no .ts in the variable name).
  • Dual build: proper CJS/ESM outputs (index.cjs / index.mjs) with matching exports for compatibility across Vite versions and config styles.
  • Refactor: drop fs-extra runtime dependency in favor of Node fs.

0.1.1

  • First modernized dual-build release.

Notes

  • If autoResolveAliasName is false, the plugin uses relative imports (./). If true or resolveAliasName is set, a Vite alias is added.
  • The generated file is written to <dir>/<outFile> at build and on changes under <dir>.