Download the PHP package nabasa/vp-wp without Composer
On this page you can find all versions of the php package nabasa/vp-wp. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package vp-wp
Short Description WordPress integration for Vite+.
License MIT
Homepage https://github.com/nabasa-dev/vp-wp
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package vp-wp
vp-wp
vp-wp brings a modern Vite+ workflow to WordPress plugins and themes.
Use it to build and serve frontend assets with WordPress-friendly defaults, a compact TypeScript API, and a lightweight PHP runtime.
Install
Install the JavaScript package with Vite+:
If you also want the PHP runtime helpers through Composer:
If you are not using Composer, copy vp-wp.php into your plugin or theme and require it manually.
Migration
Moving from @kucrut/vite-for-wp? See docs/migrating-from-vite-for-wp.md.
Vite+ config
A minimal Vite+ config looks like this:
Then run the usual Vite+ commands:
wordpress() applies WordPress-friendly defaults:
base: './'build.manifest: 'manifest.json'build.modulePreload: falsecss.devSourcemap: true- a development manifest at
vite-dev-server.json
These defaults keep asset URLs, manifests, and CSS handling aligned with WordPress expectations.
wordpressExternals() keeps common WordPress globals out of your bundle and treats React as external by default.
PHP runtime
A typical enqueue setup looks like this:
Exposed PHP runtime API:
Supported public API:
Nabasa\VitePlus\assets()creates a reusableAssetshelper.Nabasa\VitePlus\register_asset()registers an entry and extracted CSS.Nabasa\VitePlus\enqueue_asset()registers and enqueues an entry.Nabasa\VitePlus\asset_url()resolves a public asset URL.Nabasa\VitePlus\Assets::__construct()creates the helper directly.Nabasa\VitePlus\Assets::manifest_dir()gets the bound manifest directory.Nabasa\VitePlus\Assets::scope()gets the normalized scope.Nabasa\VitePlus\Assets::register()registers an entry.Nabasa\VitePlus\Assets::enqueue()registers and enqueues an entry.Nabasa\VitePlus\Assets::url()resolves an asset URL.
Advanced callable helpers:
Nabasa\VitePlus\filter_value()applies shared and scoped filters.Nabasa\VitePlus\normalize_scope()sanitizes a hook scope.Nabasa\VitePlus\get_manifest()loads and caches manifest data.Nabasa\VitePlus\parse_options()merges options with defaults.Nabasa\VitePlus\default_asset_handle()generates a default handle.Nabasa\VitePlus\stylesheet_handle()generates a deterministic style handle.Nabasa\VitePlus\prepare_asset_url()builds a manifest base URL.Nabasa\VitePlus\join_asset_url()joins a base URL and asset path.
Internal and compatibility helpers:
Nabasa\VitePlus\load_development_asset()Nabasa\VitePlus\load_production_asset()Nabasa\VitePlus\register_stylesheets()Nabasa\VitePlus\register_vite_client_script()Nabasa\VitePlus\inject_react_refresh_preamble()Nabasa\VitePlus\development_asset_src()Nabasa\VitePlus\filter_script_tag()Nabasa\VitePlus\set_script_type_attribute()Nabasa\VitePlus\should_inject_react_refresh()Nabasa\VitePlus\string_ends_with()
Core PHP filters:
nabasa_vite_plus/manifest_datanabasa_vite_plus/development_assetsnabasa_vite_plus/production_assetsnabasa_vite_plus/{scope}/manifest_datanabasa_vite_plus/{scope}/development_assetsnabasa_vite_plus/{scope}/production_assets
Use assets() when you want to bind a manifest directory once and reuse it across hooks or callbacks:
Pass a second argument to assets() when you want a plugin- or theme-specific hook namespace:
Scoped helpers still trigger the shared nabasa_vite_plus/* hooks as well as the scoped nabasa_vite_plus/{scope}/* hooks. The scope is normalized with sanitize_key().
If you prefer standalone functions, register_asset() and enqueue_asset() accept the same scope as a fourth argument.
Supported PHP options include:
handledependenciescss_dependenciescss_mediacss_onlyin_footer
During vp dev, vp-wp reads vite-dev-server.json and serves assets from the active dev server. During vp build, it reads manifest.json and registers the compiled JavaScript and extracted CSS assets.
Use asset_url() when you need the public URL for a file in the built assets directory without looking it up in the manifest:
Externals presets
Pick a preset when you want tighter control over which globals stay external:
Built-in presets:
wordpresswordpress+react
You can also extend or trim the externals map to fit your project:
Development
Credits
vp-wp is a fork and rewrite inspired by @kucrut/vite-for-wp.
Examples
Need a working reference? See examples/README.md for React, Vue, Svelte, SolidJS, and vanilla JavaScript. Each example includes the full plugin structure, Vite config, PHP bootstrap, and frontend entry for its framework.
