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 🙏

© 2025 – Pkg Stats / Ryan Hefner

vite-plugin-extract-vendors

v0.0.1

Published

A vite plugin to extract external libraries from node_modules to vendors directory to improve caching of 3rd party js files

Readme

vite-plugin-extract-vendors

Extract all the 3rd party libraries from node_modules/ into vendors/ directory of the build output directory.

This provides the following benefits to your application:

  1. Improved Browser Caching

    Why it’s important: Vendor libraries (like React, Vue, or Lodash) change less frequently than application code.

    Benefit: By separating vendors into a distinct file, users can leverage long-term caching. This allows browsers to cache these files for extended periods, reducing the need to re-download them unless the content changes.

  2. Smaller Incremental Updates

    Why it’s important: Deploying only what has changed minimizes bandwidth usage.

    Benefit: Updates to the app will only require users to download the small, application-specific chunk, leaving the vendor chunk untouched if unchanged.

This plugin is built to take full advantage of browser caching mechanism and HTTP2 - read about it on the hey blog post.

Install

npm i -D vite-plugin-extract-vendors
# or
bun i -D vite-plugin-extract-vendors
# or
yarn add -D vite-plugin-extract-vendors
# or
pnpm add -D vite-plugin-extract-vendors

Usage

import { defineConfig } from 'vite'
import { extractVendors } from 'vite-plugin-extract-vendors'

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

Options

Currently this plugin supports no options

How it works

For a standard Vite project with following node_modules directory

-> % tree node_modules -L 1
node_modules
├── @esbuild
├── @rollup
├── @types
├── dayjs
├── esbuild
├── fsevents
├── lodash
├── nanoid
├── picocolors
├── postcss
├── rollup
├── source-map-js
├── typescript
└── vite

The build output will move all the required javascript from inside node_modules to <build_output>/assets/vendor/*

-> % tree dist -L 3
dist
├── assets
│   ├── index-DeW0Mihf.js
│   ├── index-dv8c_Ups.css
│   └── vendor
│       ├── dayjs
│       └── lodash
├── index.html
└── vite.svg

Since only dayjs and lodash are referred in the application source code, they have been moved into the vendor directory. Also the vendor filenames are hashed to ensure they can be cache busted if the specific library is updated.

-> % tree dist/assets/vendor -L 2
dist/assets/vendor
├── dayjs
│   ├── dayjs.min.js-7k9w9mz7.js
│   ├── dayjs.min.js_commonjs-es-import-TtisqAT9.js
│   └── dayjs.min.js_commonjs-module-CcuaHt6D.js
└── lodash
    ├── lodash.js-BLimN7ew.js
    ├── lodash.js_commonjs-es-import-AWz_NZqP.js
    └── lodash.js_commonjs-module-BwOMhnNI.js