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 🙏

© 2024 – Pkg Stats / Ryan Hefner

webpack-php-manifest

v0.0.9

Published

Writes output file names to a PHP file.

Downloads

405

Readme

PHP Manifest from Webpack

Please note this module depends on webpack 4+.

This webpack plugin will create a PHP file in your output.path directory with a PHP class in it having two static attributes: $jsFiles and $cssFiles. These can be accessed by your PHP application to learn about what to include when rendering the frontend of the site.

Note that the php manifest is created with (node fs)[https://nodejs.org/api/fs.html] independently of the Webpack output cycle. It will therefor be created in the same location when running a standard Webpack build or Webpack Dev Server

Install

With Yarn:

yarn add webpack-php-manifest

With NPM:

npm i webpack-php-manifest

Usage

// ...in your webpack config file

const PhpManifestPlugin = require('webpack-php-manifest');
const phpManifest = new PhpManifestPlugin(options);

module.exports = {
  // ...
  plugins: [
    phpManifest
  ]
}

Available options:

output (default: "assets-manifest")

The name of the manifest file to write. Will be written to webpack's output.path directory and appended with .php.

  

path (default: "")

The relative file path to the asset files. Example:

const phpManifest = new PhpManifestPlugin({
  path: assets // Asset path will look like /assets/bundle.js
});

  

pathPrefix (default: "")

An optional absolute URL, that is prepended the asset file paths in php. Primarily used with the devServer option below.

  

devServer (default: false)

A flag that tells the plugin if webpack-dev-server is running, and adds webpack-dev-server.js to the list of JS assets in the file list.

If used, this should be passed as part of an environment or config variable. pathPrefix should also be used to point to the devServer url. Example:

const phpManifest = new PhpManifestPlugin({
  devServer: process.env.WEBPACK_DEV_SERVER, // This should be an env or config boolean
  // In this example, path prefix is included conditionally so that the prefix is only used when dev server is running
  pathPrefix:
  process.env.WEBPACK_DEV_SERVER ? `http://localhost:${port}` : null
  });

  

phpClassName (default: "WebpackBuiltFiles")

The PHP class name to use for the class. You can generally ignore this unless you have a conflicting PHP class named \WebpackBuiltFiles in your PHP environment.

Consuming the manifest

Currently there's only one implementation for consuming the generated manifest in a PHP application:

October CMS

Use the October CMS plugin called webpackassets-plugin.