npm run dev执行失败：ValidationError: 无效的选项对象

Question

npm run dev执行失败：ValidationError: 无效的选项对象

node.jsvue.jsnpmwebpack-dev-serverwebpack-cli

70

目前正在通过一些教程学习VueJS和ExpressJS，对于这些技术我仍是新手。

不管怎样，按照教程，我正在构建一个小项目，在其中有一个名为“Client”的文件夹，包含了项目的前端部分，另外一个名为“Server”的文件夹，则包含了后端。

在将提交推送到Github之前，一切都正常，但一旦推送之后，Github会发现一些漏洞，修复之后运行npm run dev就无法工作了。

尝试了多种解决方案，但都没有起作用，重新安装了可疑的模块，清理缓存之后重新安装了节点模块。

这是我得到的错误：

   npm run dev


> client@1.0.0 dev D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client
> webpack-dev-server --inline --progress --config build/webpack.dev.conf.js

D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\copy-webpack-plugin\node_modules\schema-utils\dist\validate.js:88
    throw new _ValidationError.default(errors, schema, configuration);
    ^

ValidationError: Invalid options object. Copy Plugin has been initialized using an options object that does not match the API schema.
 - options[0] misses the property 'patterns'. Should be:
   [non-empty string | object { from, to?, context?, globOptions?, toType?, force?, flatten?, transform?, cacheTransform?, transformPath?, noErrorOnMissing? }, ...] (should not have fewer than 1 item)
    at validate (D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\copy-webpack-plugin\node_modules\schema-utils\dist\validate.js:88:11)  
    at new CopyPlugin (D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\copy-webpack-plugin\dist\index.js:24:30)
    at Object.<anonymous> (D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\build\webpack.dev.conf.js:61:5)
    at Module._compile (internal/modules/cjs/loader.js:1133:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
    at Module.load (internal/modules/cjs/loader.js:977:32)
    at Function.Module._load (internal/modules/cjs/loader.js:877:14)
    at Module.require (internal/modules/cjs/loader.js:1019:19)
    at require (internal/modules/cjs/helpers.js:77:18)
    at WEBPACK_OPTIONS (D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\webpack-cli\bin\utils\convert-argv.js:114:13)
    at requireConfig (D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\webpack-cli\bin\utils\convert-argv.js:116:6)
    at D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\webpack-cli\bin\utils\convert-argv.js:123:17
    at Array.forEach (<anonymous>)
    at module.exports (D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\webpack-cli\bin\utils\convert-argv.js:121:15)
    at Object.<anonymous> (D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client\node_modules\webpack-dev-server\bin\webpack-dev-server.js:84:40)
    at Module._compile (internal/modules/cjs/loader.js:1133:30) {
  errors: [
    {
      keyword: 'required',
      dataPath: '[0]',
      schemaPath: '#/required',
      params: [Object],
      message: "should have required property 'patterns'",
      schema: [Object],
      parentSchema: [Object],
      data: [Object],
      children: [Array]
    }
  ],
  schema: {
    definitions: { ObjectPattern: [Object], StringPattern: [Object] },
    type: 'object',
    additionalProperties: false,
    properties: { patterns: [Object], options: [Object] },
    required: [ 'patterns' ]
  },
  headerName: 'Copy Plugin',
  baseDataPath: 'options',
  postFormatter: null
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! client@1.0.0 dev: `webpack-dev-server --inline --progress --config build/webpack.dev.conf.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the client@1.0.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\iheb\AppData\Roaming\npm-cache\_logs\2020-05-21T13_56_52_099Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! client@1.0.0 start: `npm run dev`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the client@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\iheb\AppData\Roaming\npm-cache\_logs\2020-05-21T13_56_52_148Z-debug.log

这是日志文件:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build:server'
1 verbose cli ]
2 info using npm@6.14.4
3 info using node@v12.16.3
4 verbose stack Error: missing script: build:server
4 verbose stack     at run (C:\Program Files\nodejs\node_modules\npm\lib\run-script.js:155:19)
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\lib\run-script.js:63:5
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:116:5
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:436:5
4 verbose stack     at checkBinReferences_ (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:391:45)
4 verbose stack     at final (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:434:3)
4 verbose stack     at then (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:161:5)
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:281:12
4 verbose stack     at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:115:16
4 verbose stack     at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
5 verbose cwd D:\projects\Fullstack web apps\VueJs ExpressJs\tab-tracker\Client
6 verbose Windows_NT 10.0.18362
7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build:server"
8 verbose node v12.16.3
9 verbose npm  v6.14.4
10 error missing script: build:server
11 verbose exit [ 1, true ]

运行 npm audit 命令会得到以下结果：

    Moderate        Cross-Site Scripting                                          

  Package         serialize-javascript                                          

  Patched in      >=2.1.1                                                       

  Dependency of   uglifyjs-webpack-plugin [dev]                                 

  Path            uglifyjs-webpack-plugin > serialize-javascript                

  More info       https://npmjs.com/advisories/1426

相关依赖项

"webpack": "^4.43.0",

"webpack-bundle-analyzer": "^3.3.2",

"webpack-cli": "^3.3.11",

"webpack-dev-server": "^3.1.11",

我希望我已经为大家提供了所有信息，如果还有疑问，我会立即提供任何帮助来澄清我的问题，正如我所说，我是web开发的新手。

更新：我一直在试图找出这种错误背后的原因，这个问题发生在更新webpack-dev-server之后。可用的版本为：

"webpack-dev-server": "^2.9.1"

带有错误的版本为：

"webpack-dev-server": "^3.11.0"

如果我忽略安全漏洞是否可以？尝试修复它们会导致此错误。

谢谢。

- Dhouibi iheb

Webpack 5有重大变化，这篇文章帮了我大忙 https://frontendguruji.com/blog/invalid-options-object-dev-server/ - Mandeep Pasbola

6个回答

47

升级到3.11后，出现了一个新的模板。

  plugins: [
    new CopyPlugin({
      patterns: [
        { from: 'source', to: 'dest' },
        { from: 'other', to: 'public' },
      ],
    }),
  ],

- aprinciple

我应该添加以下代码吗？如果是，那么在哪里添加它呢？我对 Node 完全是新手。 - Dhouibi iheb

是的，我是认真的。文件 > webpack.config.js module.exports = { } - aprinciple

1

我应该用webpack-dev-server替换CopyPlugin吗？ - Dhouibi iheb

1

我有同样的问题。 - Donutloop

const CopyWebpackPlugin = require('copy-webpack-plugin');在 "plugins:" 后面添加：new CopyWebpackPlugin({ patterns: [ { from: path.resolve(__dirname, 'src/assets/fonts'), to: path.resolve(__dirname, 'dist/fonts') } ] }), - aprinciple

9

我也遇到了同样的问题。最终，我使用以下方法解决了它：

npm install --save copy-webpack-plugin@5.1.1

- nicomstudio

6

如果您在package.json中升级到copy-webpack-plugin：^6.0.3，则以下内容应该可以正常工作，当您之前复制整个目录时：

plugins: [
    new CopyWebpackPlugin({
        patterns: [
            {
                from: "[your-src-dir]/*",
                to: "[your-dst-dir]/*",
            },
        ],
    }),
]

在目录目标和源目录名称后添加"/*"，可以修复它而不会忽略漏洞，您绝不应该这样做。

请查看https://webpack.js.org/plugins/copy-webpack-plugin/了解更多信息。

- MLH

3

这个对我有用

在webpack.config.js文件中更改CopyWebpackPlugin

new CopyWebpackPlugin({
                patterns: [
                  { from: "fonts/**", globOptions: { ignore: [`${relative(appPath, appResourcesFullPath)}/**`] } },
                  { from: "**/*.{jpg,png}", globOptions: { ignore: [`${relative(appPath, appResourcesFullPath)}/**`] } },
                ]
              }),

希望我能够帮上忙。

- roi

0

使用以下命令将 Angular 工具包版本重置为 2.3.0。

npm i @ionic/angular-toolkit@2.3.0 -E -D

- Hasee Amarathunga

网页内容由stack overflow 提供, 点击上面的

可以查看英文原文，
原文链接

- opus131 · Accepted Answer

这不是由于 webpack 或 webpack-dev-server 本身的问题，而是由于 copy-webpack-plugin 插件引起的。

升级到6.x主版本后，出现了一个破坏性的改变：现在你不能直接将带有配置模式的数组传递给 CopyWebpackPlugin 构造函数，而是需要将其包装在一个对象的 patterns 属性中并进行传递。

旧语法：

    new CopyWebpackPlugin(
      [
        { from: 'src/xxx.ext', to: 'dist/xxx.ext' },
        { from: 'src/yyy.ext', to: 'dist/yyy.ext' }
      ]
    )

新语法：

    new CopyWebpackPlugin(
      { 
        patterns: [
          { from: 'src/xxx.ext', to: 'dist/xxx.ext' },
          { from: 'src/yyy.ext', to: 'dist/yyy.ext' }
        ]
      }
    )

他们这样做是因为构造器现在支持了一个额外的options属性: https://webpack.js.org/plugins/copy-webpack-plugin/#options-1