javascript – „CommonsChunkPlugin benötigt jetzt nur noch ein einziges Argument.。。。。
巴扎黑
巴扎黑 2017-05-16 13:43:17
0
4
700

Error: Deprecation notice: CommonsChunkPlugin now only takes a single argument. Either an options
object *or* the name of the chunk.
Example: if your old code looked like this:
        new webpack.optimize.CommonsChunkPlugin('vendor', 'vendor.bundle.js')
You would change it to:
        new webpack.optimize.CommonsChunkPlugin({ name: 'vendor', filename: 'vendor.bundle.js' })
The available options are:
        name: string
        names: string[]
        filename: string
        minChunks: number
        chunks: string[]
        children: boolean
        async: boolean
        minSize: number
    at new CommonsChunkPlugin (E:\heShengWeb\manta-web\node_modules\webpack\lib\optimize\CommonsChunkPlugin.js:10:10)
    at Object.<anonymous> (E:\heShengWeb\manta-web\webpack\base.config.js:82:9)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (E:\heShengWeb\manta-web\webpack\webpack.build.config.js:5:18)

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "E:\Software\Nodejs\node.exe" "E:\Software\Nodejs\node_global\node_modules\npm\bin\npm-cli.js" "run" "build"
npm ERR! node v6.3.0
npm ERR! npm  v3.8.0
npm ERR! code ELIFECYCLE
npm ERR! mantaweb@1.0.0 build: `webpack --config webpack/webpack.build.config.js --progress --colors`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mantaweb@1.0.0 build script 'webpack --config webpack/webpack.build.config.js --progress --colors'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mantaweb package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     webpack --config webpack/webpack.build.config.js --progress --colors
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs mantaweb
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mantaweb
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     E:\heShengWeb\manta-web\npm-debug.log

Es stimmt, dass meine CommonsChunkPlugin-Konfiguration mit dem von ihm gemeldeten Fehler übereinstimmt, aber es ist nicht falsch, wenn ich sie auf dem Computer des Unternehmens so konfiguriere. Warum wird dieser Fehler auf meinem eigenen Computer gemeldet? Kann ich das Problem lösen (ich möchte diese Konfiguration nicht wirklich ändern)?

巴扎黑
巴扎黑

Antworte allen(4)
过去多啦不再A梦

不要使用webpack2.x,公司使用的配置应该是webpack1.x,2.x的配置和1.x不一样,你看下你电脑的webpack版本吧,看是不是2.x的

淡淡烟草味

CommonsChunkPlugin
版本更新了,不再支持原来的传参方式
而且应该很久以前的事了...

而且报错信息里都给出改法了:

new webpack.optimize.CommonsChunkPlugin({ 
    name: 'vendor', 
    filename: 'vendor.bundle.js', 
    minChunks: Infinity 
})
左手右手慢动作

换一个版本的库就好了,你公司上用什么版本,这里就用什么版本就好了。

小葫芦

要么把webpack更新到2.x,要么就回到webpack1.x。因为你公司用的老版本,所以说为了保持一致性。建议你改成1.x,这样也方便你的代码一致性。

Beliebte Tutorials
Mehr>
Neueste Downloads
Mehr>
Web-Effekte
Quellcode der Website
Website-Materialien
Frontend-Vorlage