Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Webpack 4.0.0.beta.1 warnings emitted

See original GitHub issue

Do you want to request a feature or report a bug? Possible bug

What is the current behavior? Emission of warnings. Not certain where these are being emitted during the build but only present in development mode.

schema id ignored BannerPlugin
schema id ignored BannerPlugin
schema id ignored BannerPlugin
schema id ignored BannerPlugin
schema id ignored BannerPlugin
schema id ignored BannerPlugin
schema id ignored BannerPlugin
schema id ignored HashedModuleIdsPlugin
schema id ignored HashedModuleIdsPlugin
schema id ignored HashedModuleIdsPlugin
schema id ignored HashedModuleIdsPlugin
(node:26081) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead

If the current behavior is a bug, please provide the steps to reproduce. Configure webpack with BannerPlugin and HashedModulePlugin. Webpack in development mode.

What is the expected behavior? No warnings should be emitted

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.

node: 8.9.4 webpack: 4.0.0.beta.1 os: macos 10.12.6

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:13 (4 by maintainers)

Top GitHub Comments

1reaction

scriptjscommented, Feb 19, 2018

@handrews I really see no barrier at all for upgrading, only whether or not we include a compiled ajv validate method or the validator in webpack. I am for keeping all packages as light as possible since webpack may be used as a lib as well as a command line bundler.

0reactions

nveenjaincommented, Feb 20, 2018

Hey, @scriptjs , guess, this is working fine for me in development, could you please upload webpack.config.js file, so that i can start working on it? I used BannerPlugin and HashedModulePlugin but it seems to be working fine. Maybe is it fixed in 4.0.beta.2??

Edit:- I don’t know whether it is happening on only my system or not, but the error for deprication is not shown during development mode, but shown during production mode. 😕

Top Results From Across the Web

webpack 4.0.0-alpha.5 feedback · Issue #6357 - GitHub

Complete changelog for 4.0.0-alpha.5 compared to version 3: Items changed from ... [new] Using System.import() now emits a warning.

How to Prevent Webpack Error after npm Install?

It seems to work now with webpack 2.1.0-beta.22 , but you got another error. This error happened because extract-text-webpack-plugin is not of the...

fork-ts-checker-webpack-plugin - npm

Webpack plugin that runs TypeScript type checker on a separate process. npm version npm beta version build status downloads commitizen friendly ...

Installation | webpack

This guide goes through the various methods used to install webpack. Prerequisites. Before we begin, make sure you have a fresh version of...

yarn install peer dependencies - You.com | The Search Engine You ...

... dependency "eslint@>=1.6.0 <4.0.0". warning Unmet peer dependency "babel-core@^6.0.0". warning Unmet peer dependency "webpack@1 || ^2.1.0-beta". warning ...