2016-12-15 7 views
13

Ich arbeite mit React/Webpack 2 etc. Ich habe Karma Test Runner und wenn ich meine Tests starte starte ich Webpack vorher, und es wirft an die Konsole Warnausgabe über Größe etc. (Ich kann es nicht reparieren, weil es Webpack-Sachen sind).So deaktivieren Sie Optimierungswarnungen in Webpack 2

Wie kann ich diese Warnungen deaktivieren? Ich habe versucht,

stats: "keine", aber es funktioniert nicht.

Vielen Dank für jede Hilfe

WARNING in ./src/modules/Module1/index.js 
There are multiple modules with names that only differ in casing. 
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic. 
Use equal casing. Compare these module identifiers: 
* C:\work\EazeGamesClient\node_modules\babel-loader\lib\index.js!C:\work\EazeGamesClient\node_modules\eslint-loader\index.js?{"fix":true}!C:\work\EazeGamesClient\src\modules\Module1\index.js 
* C:\work\EazeGamesClient\node_modules\babel-loader\lib\index.js!C:\work\EazeGamesClient\node_modules\eslint-loader\index.js?{"fix":true}!C:\work\EazeGamesClient\src\modules\module1\index.js 
    Used by 1 module(s), i. e. 
    C:\work\EazeGamesClient\node_modules\babel-loader\lib\index.js!C:\work\EazeGamesClient\node_modules\eslint-loader\index.js?{"fix":true}!C:\work\EazeGamesClient\src\routes.js 

WARNING in ./src/modules/Module1/containers/Module1.container.js 
There are multiple modules with names that only differ in casing. 
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic. 
Use equal casing. Compare these module identifiers: 
* C:\work\EazeGamesClient\node_modules\babel-loader\lib\index.js!C:\work\EazeGamesClient\node_modules\eslint-loader\index.js?{"fix":true}!C:\work\EazeGamesClient\src\modules\Module1\containers\Module1.container.js 
    Used by 1 module(s), i. e. 
    C:\work\EazeGamesClient\node_modules\babel-loader\lib\index.js!C:\work\EazeGamesClient\node_modules\eslint-loader\index.js?{"fix":true}!C:\work\EazeGamesClient\src\modules\Module1\index.js 
* C:\work\EazeGamesClient\node_modules\babel-loader\lib\index.js!C:\work\EazeGamesClient\node_modules\eslint-loader\index.js?{"fix":true}!C:\work\EazeGamesClient\src\modules\module1\containers\Module1.container.js 
    Used by 1 module(s), i. e. 
    C:\work\EazeGamesClient\node_modules\babel-loader\lib\index.js!C:\work\EazeGamesClient\node_modules\eslint-loader\index.js?{"fix":true}!C:\work\EazeGamesClient\src\modules\module1\index.js 

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (250 kB). 
This can impact web performance. 
Assets: 
    src/containers/Root.container.js (825 kB) 
    src/containers/Root.container.dev.js (821 kB) 
    src/store/configureStore.js (629 kB) 
    src/store/configureStore.dev.js (628 kB) 
    src/containers/DevTools.js (612 kB) 
    src/containers/Root.container.prod.js (389 kB) 

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (250 kB). This can impact web performance. 
Entrypoints: 
    src/containers/DevTools.js (612 kB) 
     src/containers/DevTools.js 

    src/containers/Root.container.dev.js (821 kB) 
     src/containers/Root.container.dev.js 

    src/containers/Root.container.js (825 kB) 
     src/containers/Root.container.js 

    src/containers/Root.container.prod.js (389 kB) 
     src/containers/Root.container.prod.js 

    src/store/configureStore.dev.js (628 kB) 
     src/store/configureStore.dev.js 

    src/store/configureStore.js (629 kB) 
     src/store/configureStore.js 


WARNING in webpack performance recommendations: 
You can limit the size of your bundles by using System.import() or require.ensure to lazy load some parts of your application. 
For more info visit https://webpack.js.org/guides/code-splitting/ 

P. S. Update 1

webpack.testing.config

let process = require("process"), 
    autoprefixer = require('autoprefixer'), 
    precss = require('precss'), 

    webpack = require("webpack"), 
    helpers = require("./helpers"), 

    ExtractTextPlugin = require("extract-text-webpack-plugin"), 
    CssSourcemapPlugin = require("css-sourcemaps-webpack-plugin"), 

    srcName = "src"; 

module.exports = { 
    entry : { 
     "vendor" : ["react", "react-dom", "react-router", "redux", "react-router-redux"], 
     "app" : helpers.root(srcName, "index.js") 
    }, 
    output : { 
     path : helpers.root("dist"), 
     publicPath : "/", 
     filename : "[name].[hash].bundle.js", 
     chunkFilename : "[id].[hash].bundle.chunk.js" 
    }, 
    context : helpers.root(srcName), 

    module : { 
     rules : [ 
      { 
       enforce : 'pre', 
       test : /\.jsx?$/, 
       loader : 'eslint-loader', 
       options: { 
        fix: true, 
       }, 
       include: helpers.root(srcName) 
      }, 
      { 
       test : /\.jsx?$/, 
       loaders : [ 
        'babel-loader', 
       ], 
       exclude : /node_modules/ 
      }, 
      { 
       test : /\.css$/, 
       loaders : [ 
        'style-loader', 
        'css-loader?modules', 
        'postcss-loader', 
       ], 
      }, 
     ], 
    }, 

    stats: "none", 

    devtool: 'inline-source-map', 


    plugins : [ 
     new webpack.LoaderOptionsPlugin({ 
      options : { 
       eslint : { 
        configFile : '.eslintrc', 
        failOnWarning : false, 
        failOnError : false 
       } 
      } 
     }), 
     new CssSourcemapPlugin(), 
     new ExtractTextPlugin("[name].[hash].css") 
    ], 

    performance: { 
     hints: false 
    } 
}; 

Antwort

21

Basierend auf Protokollen gibt es zwei Arten von Warnungen

  1. WARNUNG ... Größenbegrenzung - um es zu beheben hinzufügen zu webpack.config Option performance

    performance: { 
        hints: false 
    } 
    

    Empfohlene disable hints im Entwicklungsmodus jedoch in Produktionsmodus aktiviert

  2. WARNUNG Es gibt mehrere Module mit Namen, die nur in Gehäusen unterscheiden. - diese Warnung auf Windows-Betriebssystem im Zusammenhang scheint, gibt es issue auf Github diskutiert, wo dieses Problem

+1

Es funktioniert! Ich habe es nur zur webpack-config hinzugefügt, aber ich habe vergessen, dass ich in meinem Karma nur Module aus dieser conf.file verwendet habe. Also habe ich gerade die Perfomance-Regel zur Karma.conf hinzugefügt. Vielen Dank, mein Freund! – Velidan

+0

@ Velidan willkommen) –