alexpalombaro/modernizr-webpack-plugin

Issues

• Not working with webpack@^5.0.0

  #42 opened 4 years ago by ayxos
  4

• Is this project dead?

  #33 opened 4 years ago by rejas
  3

• Please add support for Webpack 4.8.3

  #27 opened 5 years ago by blachawk
  2

• Feature test suggestion: Update modernizr package for IntersectionObserver

  #32 opened 5 years ago by asherccohen
  0

• how to expose css-classes of features to html?

  #14 opened 8 years ago by 0xgeert
  5

• Depending on the most recent version breaks npm security audit

  #31 opened 5 years ago by sergeymorkovkin
  1

• Include modernizr in webpack output file.

  #10 opened 9 years ago by GreenGremlin
  4

• Don't set NODE_ENV in the top level of the plugin's index.js

  #30 opened 6 years ago by nerdkid93
  0

• webpack 4.5 produces warning about Tapable.plugin is deprecated

  #26 opened 6 years ago by bigfish
  6

• Add classes to html element

  #15 opened 6 years ago by jonathandion
  1

• HTML Webpack Plugin

  #22 opened 7 years ago by gregorskii
  4

• Update to latest stable version

  #24 opened 7 years ago by chrisdholt
  1

• Add an option for injecting the Modernizr build output directly into the HTML

  #23 opened 7 years ago by Hubro
  0

• Customizr Support?

  #21 opened 7 years ago by ajbrun
  0

• html-webpack-plugin 2.x

  #13 opened 9 years ago by jantimon
  1

• [hash] vs [chunkhash]

  #19 opened 7 years ago by TigerC10
  1

• Install modernizr required ? [Question]

  #18 opened 7 years ago by Squidies
  2

• Multiple instances of `HtmlWebpackPlugin` breaks compilation

  #12 opened 9 years ago by SimenB
  0

• setClasses missing from output

  #8 opened 9 years ago by joshgillies
  6

• Build failure with NODE_ENV=production

  #9 opened 9 years ago by GreenGremlin
  3

• Missing ouputPath

  #1 opened 9 years ago by SimenB
  2