PHPackages dimezilla/wp\_manifest\_loader - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. dimezilla/wp\_manifest\_loader ActiveLibrary[Utility & Helpers](/categories/utility) dimezilla/wp\_manifest\_loader ============================== A package intended for wordpress that provides an automatic way to register and enqueue scripts read via a manifest file built by a npm bundler service v1.0.0(7y ago)038MITPHP Since Feb 14Pushed 7y ago1 watchersCompare [ Source](https://github.com/DimeZilla/wp_manifest_loader)[ Packagist](https://packagist.org/packages/dimezilla/wp_manifest_loader)[ RSS](/packages/dimezilla-wp-manifest-loader/feed)WikiDiscussions master Synced 2w ago READMEChangelogDependencies (1)Versions (2)Used By (0) WordPress Manifest Loader ========================= [](#wordpress-manifest-loader) This library provides a simple class that will read a `manifest.json` and automatically register and enqueue the scripts found within. A manifest.json is typically a file that is produced by a bundler like webpack as part of a production build. It could be something that looks like this: ``` { "main.css": "main.63d564d3327e37de652f.css", "main.js": "main-63d564d3327e37de652f.js" } ``` Installation ------------ [](#installation) Install via composer: ``` composer require dimezilla/wp_manifest_loader ``` Basic Usage ----------- [](#basic-usage) It's pretty simple. For the purpose of the following example, I'm going to assume that you are using this in a plugin. 1. The first thing you should do is create the class: ``` $loader = new MANIFEST_LOADER\AssetLoader(\plugin_dir_url(__FILE__), dirname(__FILE__), 'radcampagin', '0.0'); ``` Here's all of the arguments that the assetloader takes in the order in which they are accepted: - $plugin\_url - string - the url to the the present project path - $plugin\_path - string - the path to the present project - $tag\_prefix - string - the tag prefix for the project - $version - string - the version number associated with the assets - $distribution\_path - string - the path from the project root to the distribution files and where the manifest.json is located - $manifest\_filename - string - the name of the manifest.json file in case it has a different name - $load\_config - boolean - look for a config file and load it automatically - $read\_manifest - boolean - look for the manifest and read it automatically In the above example, we are telling the asset loader that the url is the wordpress generated url for the plugin project's path. Then we are telling the asset loader that the directory path to our project is this current directory of our file. Next we are telling the loader that the plugin tag prefix is 'radcampaign'. This means that the asset loader will ascribe a handle prefixed with 'radcampaign/' for let's say a file called main.js. Thus the handle would be 'radcampaign/main.js'. So if you want o use it as a script dependency later, in another script, this is how you would use it. 2. Next, call registerAssets inside some sort of `wp_enqueue_scripts` hook ``` add_action('wp_enqueue_scripts', function () use ($loader) { $loader->registerAssets(); }); ``` `registerAssets` by default automatically enqueues the assets it finds. To prevent this from happening you can call register assets like so: ``` add_action('wp_enqueue_scripts', function () use ($loader) { $loader->registerAssets(false); // do some stuff .... $loader->enqueueAssets(); }); ``` Advanced Usage -------------- [](#advanced-usage) ### Asset Specific Configuration [](#asset-specific-configuration) This package has support for a `asset-loader.config.json` to be placed in the same director as the `$plugin_path` setting when the class is instantiated. This file must be valid json and is a dictionary keyed by the script key found in the manifest file. Borrowing from our example above, here's what a possible configuration might look like: ``` { "main.js": { "dependencies": ["jquery", "lodash"], "version": "0.1", "in_footer": true }, "main.css": { "dependencies": ["bootstrap"], "version": "1.0", "media": "screen" } } ``` This file would register our main.js script with the jquery and lodash dependencies. It would assign a version of 0.1, and load the script in the footer. This would also register main.css with the a bootstrap dependency, give it a version of 1.0 and specify a "screen" media for the css. ### Instantiating the loader [](#instantiating-the-loader) You don't have to use `new MANIFEST_LOADER\AssetLoader` to craete the class. You can also create it through it's static method `MANIFEST_LOADER\AssetLoader::create`. This method takes all of the same arguments as the `__construct` method. ### Deferring the reading of local files [](#deferring-the-reading-of-local-files) By default, when the loader is created, it will load config if an `asset-loader.config.json` is found. It will also try and find the manifest file and read that as well. You can turn this behavior off when creating the class by doing the following: ``` $loader = new MANIFEST_LOADER\AssetLoader(\plugin_dir_url(__FILE__), dirname(__FILE__), 'radcampagin', '0.0', 'dist', false, false); // or $loader = MANIFEST_LOADER\AssetLoader::create(\plugin_dir_url(__FILE__), dirname(__FILE__), 'radcampagin', '0.0', 'dist', false, false); // and then later, whenever you are ready $loader->loadConfig(); // will look for the asset-loader.config.json file and read the configuration $loader->readManifest(); // will look for the manifest file and load it into the class ``` ### `assetURL` & `assetPath` [](#asseturl--assetpath) After the manifest has been loaded, you can get any of the file paths or urls by running the following ``` $loader->assetURL('main.js'); // will return the url for the file - i.e http:://example.com/wp-content/plugins/example-plugin/dist/main-a80c136812df324d6bcf.js $loader->assetPath('main.js'); // will return the full file path for the file - i.e. /var/www/html/wp-content/plugins/example-plugin/dist/main-a80c136812df324d6bcf.js ``` ### Changing initial configuration [](#changing-initial-configuration) If after you create the loader you want to do something like lets say changing the default version used you can use one of the setters to change. In this case you can run `$loader->setVersion('2.5');` and this will change the default version to "2.5". You can use a getter function retrieve the default version by running `$loader->getVersion();` and this will return the instance default version. All of the setters return the class instance so that you may chain them like this: ``` $loader->setVersion('2.5') ->setDistributionPath('lib') ->setPluginPath('/var/www/html/wp-content/plugins/example/src'); ``` Here's all of the setters and their corresponding getters: - `setPluginPath` && `getPluginPath` - `setPluginUrl` && `getPluginUrl` - `setDistributionPath` && `getDistributionPath` - `setManifestFilename` && `getManifestFilename` - `setVersion` && `getVersion` - `setTagPrefix` && `getTagPrefix` Again all of these set functions return the class instance. All of the get functions take no arguments and return the value. ### Health Score 26 — LowBetter than 41% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity7 Limited adoption so far Community7 Small or concentrated contributor base Maturity60 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 2692d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/3506636?v=4)[Joshua](/maintainers/DimeZilla)[@DimeZilla](https://github.com/DimeZilla) --- Top Contributors [![DimeZilla](https://avatars.githubusercontent.com/u/3506636?v=4)](https://github.com/DimeZilla "DimeZilla (10 commits)") ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/dimezilla-wp-manifest-loader/health.svg) ``` [![Health](https://phpackages.com/badges/dimezilla-wp-manifest-loader/health.svg)](https://phpackages.com/packages/dimezilla-wp-manifest-loader) ``` ### Alternatives [sastrawi/sastrawi PHP library for stemming Indonesian language (Bahasa Indonesia) 44075.7k4](/packages/sastrawi-sastrawi) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)