Registry / web-framework / wordpress-vite-plugin

wordpress-vite-plugin

JSON →
library1.6.0jsnpmunverified

WordPress Vite Plugin (v1.6.0) is a Vite plugin that integrates Vite into WordPress theme/plugin development, providing hot module replacement, asset bundling, and automatic enqueuing. It supports Vite 3-8, requires Node >=16, ships TypeScript types, and offers a streamlined setup with minimal configuration compared to manual webpack or custom build setups. Release cadence is irregular; key differentiators include native HMR in WordPress admin, automatic asset manifest parsing, and compatibility with both Classic and Block themes. v1.6 introduces support for Vite 6 and 7/8 prereleases.

npm install wordpress-vite-plugin
INSTALL
IMPORT
SIG · WORDPRESS-VITE-PLU
W
wordpress-vite-plugin
web-frameworkjavascriptv1.6.0
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18223 runs
build_error
glibc
node 18223 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

wordpressVitePlugin
import wordpressVitePlugin from 'wordpress-vite-plugin'
const wordpressVitePlugin = require('wordpress-vite-plugin')
Package is ESM-only since v1, CommonJS require() will not work.
wordpressVitePlugin
const plugin = require('wordpress-vite-plugin'); module.exports = plugin.default || plugin;
const { wordpressVitePlugin } = require('wordpress-vite-plugin')
If using require() in a CommonJS context, you must access the default export via .default
WordpressVitePluginOptions
import type { WordpressVitePluginOptions } from 'wordpress-vite-plugin'
import { WordpressVitePluginOptions } from 'wordpress-vite-plugin'
This is a TypeScript type, not a value, so use import type to avoid bundling runtime.

Minimal Vite config for WordPress plugin: sets up HMR and build with two input files and custom output structure.

// vite.config.js import { defineConfig } from 'vite'; import wordpressVitePlugin from 'wordpress-vite-plugin'; export default defineConfig({ plugins: [wordpressVitePlugin({ input: ['js/main.js', 'css/style.css'], wordpressPluginName: 'my-plugin', })], build: { rollupOptions: { output: { entryFileNames: 'js/[name].js', chunkFileNames: 'js/[name]-[hash].js', assetFileNames: 'css/[name][extname]', }, }, }, });
Debug
Known issues
breakingVite 3+ required; Vite 2 and earlier are not supported.
fix
Upgrade Vite to ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0
affects: <1.0.0
breakingDefault export changed from a function to a plugin factory in v1.0; calling wordpressVitePlugin() now returns a Vite plugin object.
fix
Use wordpressVitePlugin({...}) instead of wordpressVitePlugin as a direct plugin.
affects: >=1.0.0
deprecatedThe 'config' option has been replaced by 'pluginOptions' for advanced configuration.
fix
Rename 'config' to 'pluginOptions'.
affects: >=1.4.0
gotchaHMR dev server must be running; for WordPress admin integration, set WP_HOME constant in wp-config.php to match Vite dev server origin.
fix
Add define('WP_HOME', 'http://localhost:5173'); to wp-config.php during development.
affects: >=1.0.0
gotchaAsset manifest (dist/.vite/manifest.json) is required for production builds; ensure build.manifest is true in Vite config.
fix
Set build.manifest: true in vite.config.js.
affects: >=1.0.0
Errors
Common errors & fixes
Cannot find module 'wordpress-vite-plugin'
Package not installed or ESM-only import used in CommonJS environment.
fix
Run npm install wordpress-vite-plugin --save-dev and ensure package.json has 'type': 'module' or use .mjs extension.
wordpressVitePlugin is not a function
Default import missing or using named import incorrectly in CommonJS.
fix
Use import wordpressVitePlugin from 'wordpress-vite-plugin' in ESM, or const plugin = require('wordpress-vite-plugin').default in CommonJS.
Plugin 'wordpress-vite-plugin' does not have a 'name' property
The imported value is not a properly initialized plugin factory; likely called the factory incorrectly.
fix
Ensure you call wordpressVitePlugin() as a function with options object in the plugins array.
ENOENT: no such file or directory, open '.../dist/.vite/manifest.json'
Production build missing manifest file; build.manifest is not set to true in Vite config.
fix
Add build: { manifest: true } to vite.config.js.
Upgrade
Version history
1.6.0latest on npm
Audit
Dependencies
viterequiredPeer dependency; required at runtime to provide Vite dev server and build capabilities
Agent activity
23 hits · last 30 days
node
20
OpenAI (training)
1
Resources
wordpress-vite-plugin — npm install wordpress-vite-plugin · libregistry