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

plonetheme-webpack-plugin

v2.2.0

Published

Webpack plugin for building Plone themes

Downloads

12

Readme

Plone Webpack Plugin

plonetheme-webpack-plugin provides a Webpack (4.x) plugin and presets for building completely Webpack managed themes for Plone 5, using the resources shipped with a Plone release.

While this plugin can be used to build any kind of bundles with webpack, due to the lack of documentation, this best used with plonetheme.webpacktemplate.

In short, this package makes it possible to build Plone-themes with Webpack so that all possible frontend resources are managed by Webpack and are built from the package versions shipped with Plone.

This plugin requires a running Plone site while executing the initial build (or webpack-dev-server) and does several things, which can be explained best with the following minimal webpack.config.js. After the initial build, the plugin can rely on its cache persisted at ./plone of the current working directory.

const path = require('path');
const merge = require('webpack-merge');

const PlonePlugin = require('plonetheme-webpack-plugin');

const SITENAME = process.env.SITENAME || 'Plone';
const THEMENAME = process.env.THEMENAME || 'mytheme';
const PUBLICPATH = process.env.PUBLICPATH || '/' + SITENAME + '/++theme++' + THEMENAME + '/';

const PATHS = {
  src: path.join(__dirname, 'src', THEMENAME),
  build: path.join(__dirname, 'theme', THEMENAME)
};

const PLONE = new PlonePlugin({
  portalUrl: 'http://localhost:8080/' + SITENAME,
  publicPath: PUBLICPATH,
  sourcePath: PATHS.src,
  momentLocales: ['ca', 'fi'],
  debug: false
});

const common = {
  entry: {
   'default': path.join(PATHS.src, 'default'),
  },
  output: {
    path: PATHS.build
  },
  resolve: {
    extensions: ['.js', '.json'],
  },
  module: {
    rules: [
      {
        test: /\.js$/,
        use: [
          {
            loader: 'babel-loader',
            options: {
              cacheDirectory: true,
            }
          }
        ],
        include: PATHS.src
      }
    ]
  }
};

switch(path.basename(process.argv[1])) {
  case 'webpack':
    module.exports = merge(PLONE.production, common);
    break;

  case 'webpack-dev-server':
    module.exports = merge(PLONE.development, common, {
      entry: [
        path.join(PATHS.src, 'default')
      ]
    });
    break;
}

if (PLONE.config.debug) {
  console.log(module.exports);
}
  1. This example expects a Plone theme source at ./src/mytheme and it builds a complete theme into ./theme/mytheme.
  2. At first, PlonePlugin is initialized with the address for the running Plone site and other required information.
  3. While initializing itself, PlonePlugin reads RequireJS and LESS configuration from Plone and prepares mergeable Webpack presets into the plugin instance. The presets already include the plugin itself.
  4. A common Webpack configuration is defined with the bundle to build. Please, see plonetheme.webpacktemplate for example bundle and example theme mockups (where all final bundles get injected).
  5. Finally, PlonePlugin-presets for production and development are merged with the custom configuration (which may also override values in those presets).

See the plugin sources for the preset details.

Versions in 0.x series of this plugin were compatible with Webpack 1.x. Versions in 1.x series of this plugin were compatible with Webpack 2.x.