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

static-generator-webpack-plugin

v3.1.2

Published

Minimal, unopinionated static site generator powered by webpack

Downloads

4

Readme

static generator webpack plugin


This is a fork of static-site-generator-webpack-plugin that allows for dynamic paths at runtime using webpack contexts.


Minimal, unopinionated static site generator powered by webpack.

Install

$ npm install static-generator-webpack-plugin --save-dev

Usage

Ensure you have webpack installed, e.g. npm install -g webpack

webpack.config.js

const StaticGeneratorPlugin = require('static-generator-webpack-plugin');

module.exports = {
  entry: {
    'main': './index.js'
  },

  output: {
    filename: 'index.js',
    path: 'dist',
    /* IMPORTANT!
     * You must compile to UMD or CommonJS
     * so it can be required in a Node context: */
    libraryTarget: 'umd'
  },

  plugins: [
    new StaticGeneratorPlugin('main', {
      // Properties here are passed to
      // the exported render function
      greet: 'Hello'
    })
  ]

};

index.js

// creates an object with filepaths as keys
// and modules as values
function requireAll(context) {
  return context.keys().reduce((modules, key) => {
    modules[key] = context(key);
    return modules;
  }, {});
}

module.exports = {
  // expects a render function that takes a module
  // and returns a string
  render: (Page, locals, done) => {
    done(
      null,
      '<!DOCTYPE html>' +
      Dom.renderToStaticMarkup(<Page locals={locals} />)
    )
  },
  // expects an object with input filepaths for keys
  // and module definitions as values
  pages: Object.assign(
    {},
    requireAll(require.context('./pages/', true, /\.jsx$/))
  ),
  // expects a function that defines output path
  // based on input module filepath
  transform: inputPath => {
    return inputPath
      .replace('./', '')
      .replace(/\.jsx/, '.html');
  }
}

Default locals

// The list of input paths being rendered:
locals.paths

// The input filepath currently being rendered:
locals.path;

// the list of output paths being rendered
locals.outputPaths;

// The output filepath currently being rendered:
locals.outputPath;

// a helper string for resolving absolute paths 
// to root.  eg. `../..` or `.`
locals.baseHref;

// An object containing all assets:
locals.assets;

// Advanced: Webpack's stats object:
locals.webpackStats;

Any additional locals provided in your config are also available.

Scope

If required, you can provide an object that will exist in the global scope when executing your render function. This is particularly useful if certain libraries or tooling you're using assumes a browser environment.

For example, when using Webpack's require.ensure, which assumes that window exists:

const scope = { window: {} };

module.exports = {
  ...,
  plugins: [
    new StaticGeneratorPlugin('main', locals, scope)
  ]
}

Related projects

License

MIT License