tcoopman/image-webpack-loader

Use `optionalDependencies` for imagemin plugins

Open

#53 opened on Nov 10, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (2,037 stars) (147 forks)batch import
help wanted

Description

Why?

  1. It reduces the size of the package (including dependencies).
  2. Lack of packets that are not using in the application (inside node_modules).
  3. Faster loading plugin (require, import).
  4. We enable the user to decide which plugins to use the usual options.
  5. No need to keep track of versions of plug-ins and constantly update them.

I can do PR, but this major release. Also i can help with repo (https://github.com/tcoopman/image-webpack-loader/issues/47).

Contributor guide

Tech stack
javascriptnodejs
Domain
build systemperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsnpmWebpack
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review the current dependencies in package.json. Implement optionalDependencies for each imagemin plugin and update the loader code in index.js to handle missing plugins gracefully. Test with and without each plugin. Update the README to explain the optional nature.