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-image-processor-loader

v1.4.4

Published

A webpack loader for processing images.

Downloads

19

Readme

webpack-image-processor-loader

A webpack loader for processing images.

This loader enable you to process sharp on images when webpack bundles them.

According to sharp:

This module supports reading JPEG, PNG, WebP, TIFF, GIF and SVG images.

Output images can be in JPEG, PNG, WebP and TIFF formats as well as uncompressed raw pixel data.

Install

Install with npm:

npm install --save-dev webpack-image-processor-loader

Install with yarn:

yarn add --dev webpack-image-processor-loader

Usage

If you only want to process some but not all images use webpack's oneOf.

webpack.config.js

module.exports = {
  // ...
  // IMPORTANT: Don't forget to enable caching!
  //            It's also recommended to use a persistant folder (unlike the default node_modules/.cache/webpack).
  cache: {
    type: 'filesystem',
    cacheDirectory: '/user/tom/persistant_folder/'
  },
  // ...
  module: {
    rules: [
      // ...
      {
        test: /\.(png|jpe?g|webp|tiff?)/i,
        loader: 'webpack-image-processor-loader',
        options: {
          pipelines: {
            thumbnail: sharp => sharp.resize(1280, 720).toFormat("jpeg"),

            backgroundSmall: sharp =>
              sharp.resize(500, 500)
                   .runPipeline("background")
                   .toFormat("webp", { quality: 60 }),

            backgroundBig: sharp =>
              sharp.resize(1000, 1000)
                   .runPipeline("background")
                   .toFormat("jpeg", { quality: 90 }),

            background: sharp =>
              sharp.flip()
                   .flop()
                   .rotate(45)
                   .sharpen()
                   .normalize()
                   .toColorspace("srgb")
          }
        }
      },
    ],
  },
};

pipelines

The pipelines option is an object. Each property is one pipeline and the property name is the name of the pipeline. You can call it as an url parameter like this:


require('./img/picture.jpg?pipeline=thumbnail')

A pipeline is a function that specifies how to process with sharp.

See sharp's API page for details.

The function is called with a parameter named sharp, it is an object of the same type as the sharp()'s in sharp's API page.

The return type of the function should be an sharp object.

Custom .runPipeline() method

The loader adds a custom .runPipeline() method to the sharp object. It enables you to run another pipeline function so you dont have to repeat yourself as often.

file-loader

You can also include every option the file-loader provides. See file-loader's npm page for details

module.exports = {
  // ...
  module: {
    rules: [
      // ...
      {
        test: /\.(png|jpe?g|webp|tiff?)/i,
        loader: 'webpack-image-processor-loader',
        options: {
          pipelines: {
            // ...
          },
          name: '[name]-[pipelinename]-[contenthash].[ext]',
          outputPath: 'images',
          esModule: true
          // For more options see the file-loader package
        }
      },
    ],
  },
};

For the name options you can additionally use [pipelinename]. It will be replaced by the pipeline name or "original" if there is no pipeline defined.