- configuration.module has an unknown property 'loader' 问题解决

最新推荐文章于 2023-07-11 10:35:54 发布
转载 最新推荐文章于 2023-07-11 10:35:54 发布 · 243 阅读 · 0 ·
CC 4.0 BY-SA版权
原文链接：http://www.cnblogs.com/zuojiayi/p/9342452.html
文章标签：

#webpack #ViewUI

 

错误提示：

Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.module has an unknown property 'loader'. These properties are valid:
   object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, loaders?, noParse?, rules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp?, strictExportPresence?, strictThisContextOnImports? }
   -> Options affecting the normal modules (`NormalModuleFactory`).

 

webpack v2 之后都用rules 了，把module里的那个loaders改成rules

     

 

转载于:https://www.cnblogs.com/zuojiayi/p/9342452.html

webpack高版本configuration.module has an unknown property ‘loaders‘
qq_35273097的博客
10-10 1625
webpack高版本报错configuration.module has an unknown property 'loaders'
react webpack 启动报错
m0_70760586的博客
06-17 1218
node scripts/start.js报错如下Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. - configuration has an unknown property 'optimization'. These properties are valid: object { amd?, bail
configuration.module has an unknown property 'loaders'. These properties arevalid: 解决办法
热门推荐
hph的博客
01-02 1万+
把module里的那个  loaders  改成  rules  即可
配置webpack module时 configuration.module has an unknown property 'loaders'报错的问题
weixin_40336827的博客
03-29 2832
我在项目中使用的是gulp构建的 在运行gulp的时候 报了如下错误 ： WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. - con...
react之webpack报错：- configuration.module has an unknown property 'loaders'. These properties are valid
weixin_40200876的博客
07-25 492
module.exports = { entry: './src/app.js', output: { path: path.resolve(__dirname,'./bin'), filename: 'app.bundle.js' }, module: { loa...
- configuration.module has an unknown property 'loaders'. These properties are valid:
qq_37235231的博客
03-29 1366
把module里的那个loaders改成rules
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. - configuration.module.rules[2] has an unknown property 'type'. These properties are valid: object { enforce?, exclude?, include?, issuer?, loader?, loaders?, oneOf?, options?, parser?, query?, resource?, resourceQuery?, compiler?, rules?, test?, use? } -> A rule
06-06
然而，根据用户提供的信息，出现了 `Invalid property 'type' in module.rules` 的错误。这表明在 `module.rules` 中使用了无效的属性 `type`[^1]。 Webpack 的官方文档中明确规定了 `module.rules` 的合法属性列表...
vite v5.4.19 building for production... transforming (7) node_modules\vue\dist\vue.runtime.esm-bundler.js[@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead of ::v-deep <inner-selector>. [@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead of ::v-deep <inner-selector>. [@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead of ::v-deep <inner-selector>. ✓ 136 modules transformed. dist/index.html 0.43 kB │ gzip: 0.28 kB dist/assets/index-fRN9Gjbe.css 3.24 kB │ gzip: 1.18 kB dist/assets/home-DQ_X9V7Z.css 7.87 kB │ gzip: 1.90 kB dist/assets/index-BweWhkAY.js 92.14 kB │ gzip: 36.63 kB dist/assets/home-BPoxZqS0.js 199.11 kB │ gzip: 69.78 kB ✓ built in 1.29s • electron-builder version=24.13.3 os=10.0.26100 • loaded configuration file=package.json ("build" field) ⨯ Invalid configuration object. electron-builder 24.13.3 has been initialized using a configuration object that does not match the API schema. - configuration.extraResources[0] has an unknown property &#39;noExtract&#39;. These properties are valid: object { filter?, from?, to? } How to fix: 1. Open https://www.electron.build/configuration/configuration 2. Search the option name on the page (or type in into Search to find across the docs). * Not found? The option was deprecated or not exists (check spelling). * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root. - configuration.win.extraResources[0] has an unknown property &#39;noExtract&#39;. These properties are valid: object { filter?, from?, to? } How to fix: 1. Open https://www.electron.build/configuration/win 2. Search the option name on the page (or type in into Search to find across the docs). * Not found? The option was deprecated or not exists (check spelling). * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root. failedTask=build stackTrace=ValidationError: Invalid configuration object. electron-builder 24.13.3 has been initialized using a configuration object that does not match the API schema. - configuration.extraResources[0] has an unknown property &#39;noExtract&#39;. These properties are valid: object { filter?, from?, to? } How to fix: 1. Open https://www.electron.build/configuration/configuration 2. Search the option name on the page (or type in into Search to find across the docs). * Not found? The option was deprecated or not exists (check spelling). * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root. - configuration.win.extraResources[0] has an unknown property &#39;noExtract&#39;. These properties are valid: object { filter?, from?, to? } How to fix: 1. Open https://www.electron.build/configuration/win 2. Search the option name on the page (or type in into Search to find across the docs). * Not found? The option was deprecated or not exists (check spelling). * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root. at validate (D:\admin-project\guangxi-quan-vue3\node_modules\@develar\schema-utils\dist\validate.js:86:11) at validateConfig (D:\admin-project\guangxi-quan-vue3\node_modules\app-builder-lib\src\util\config.ts:240:3) at Packager._build (D:\admin-project\guangxi-quan-vue3\node_modules\app-builder-lib\src\packager.ts:345:5) at Packager.build (D:\admin-project\guangxi-quan-vue3\node_modules\app-builder-lib\src\packager.ts:340:12) at executeFinally (D:\admin-project\guangxi-quan-vue3\node_modules\builder-util\src\promise.ts:12:14)
06-07
我们有两个主要问题需要解决：1.electron-builder24.13.3的配置错误（关于electronDownload.mirrorOptions和win.extraResources[0].noExtract）2.Vue3中::v-deep已废弃的警告首先，针对electron-builder的配置错误：...
> flowoutdemo@0.0.0 electron:build > set ELECTRON_MIRROR=https://github.com/electron/electron/releases/download/ && npm run build && electron-builder -c.extraMetadata.main=electron/main.js > flowoutdemo@0.0.0 build > vite build vite v5.4.19 building for production... transforming (10) vite\preload-helper.js[@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead of ::v-deep <inner-selector>. [@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead of ::v-deep <inner-selector>. [@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead of ::v-deep <inner-selector>. ✓ 136 modules transformed. dist/index.html 0.43 kB │ gzip: 0.28 kB dist/assets/index-fRN9Gjbe.css 3.24 kB │ gzip: 1.18 kB dist/assets/home-DQ_X9V7Z.css 7.87 kB │ gzip: 1.90 kB dist/assets/index-BweWhkAY.js 92.14 kB │ gzip: 36.63 kB dist/assets/home-BPoxZqS0.js 199.11 kB │ gzip: 69.78 kB ✓ built in 1.27s • electron-builder version=26.0.12 os=10.0.26100 • loaded configuration file=package.json ("build" field) ⨯ Invalid configuration object. electron-builder 26.0.12 has been initialized using a configuration object that does not match the API schema. - configuration.win should be one of these: object { appId?, artifactName?, asar?, asarUnpack?, azureSignOptions?, compression?, cscKeyPassword?, cscLink?, defaultArch?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, legalTrademarks?, protocols?, publish?, releaseInfo?, requestedExecutionLevel?, signAndEditExecutable?, signExts?, signtoolOptions?, target?, verifyUpdateCodeSignature? } | null -> Options related to how build Windows targets. Details: * configuration.win has an unknown property &#39;sign&#39;. These properties are valid: object { appId?, artifactName?, asar?, asarUnpack?, azureSignOptions?, compression?, cscKeyPassword?, cscLink?, defaultArch?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, legalTrademarks?, protocols?, publish?, releaseInfo?, requestedExecutionLevel?, signAndEditExecutable?, signExts?, signtoolOptions?, target?, verifyUpdateCodeSignature? } * configuration.win has an unknown property &#39;signingHashAlgorithms&#39;. These properties are valid: object { appId?, artifactName?, asar?, asarUnpack?, azureSignOptions?, compression?, cscKeyPassword?, cscLink?, defaultArch?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, legalTrademarks?, protocols?, publish?, releaseInfo?, requestedExecutionLevel?, signAndEditExecutable?, signExts?, signtoolOptions?, target?, verifyUpdateCodeSignature? } How to fix: 1. Open https://www.electron.build/win 2. Search the option name on the page (or type in into Search to find across the docs). * Not found? The option was deprecated or not exists (check spelling). * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root. failedTask=build stackTrace=ValidationError: Invalid configuration object. electron-builder 26.0.12 has been initialized using a configuration object that does not match the API schema. - configuration.win should be one of these: object { appId?, artifactName?, asar?, asarUnpack?, azureSignOptions?, compression?, cscKeyPassword?, cscLink?, defaultArch?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, legalTrademarks?, protocols?, publish?, releaseInfo?, requestedExecutionLevel?, signAndEditExecutable?, signExts?, signtoolOptions?, target?, verifyUpdateCodeSignature? } | null -> Options related to how build Windows targets. Details: * configuration.win has an unknown property &#39;sign&#39;. These properties are valid: object { appId?, artifactName?, asar?, asarUnpack?, azureSignOptions?, compression?, cscKeyPassword?, cscLink?, defaultArch?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, legalTrademarks?, protocols?, publish?, releaseInfo?, requestedExecutionLevel?, signAndEditExecutable?, signExts?, signtoolOptions?, target?, verifyUpdateCodeSignature? } * configuration.win has an unknown property &#39;signingHashAlgorithms&#39;. These properties are valid: object { appId?, artifactName?, asar?, asarUnpack?, azureSignOptions?, compression?, cscKeyPassword?, cscLink?, defaultArch?, detectUpdateChannel?, disableDefaultIgnoredFiles?, electronLanguages?, electronUpdaterCompatibility?, executableName?, extraFiles?, extraResources?, fileAssociations?, files?, forceCodeSigning?, generateUpdatesFilesForAllChannels?, icon?, legalTrademarks?, protocols?, publish?, releaseInfo?, requestedExecutionLevel?, signAndEditExecutable?, signExts?, signtoolOptions?, target?, verifyUpdateCodeSignature? } How to fix: 1. Open https://www.electron.build/win 2. Search the option name on the page (or type in into Search to find across the docs). * Not found? The option was deprecated or not exists (check spelling). * Found? Check that the option in the appropriate place. e.g. "title" only in the "dmg", not in the root. at validate (D:\admin-project\guangxi-quan-vue3\node_modules\@develar\schema-utils\dist\validate.js:86:11) at validateConfiguration (D:\admin-project\guangxi-quan-vue3\node_modules\app-builder-lib\src\util\config\config.ts:239:3) at Packager.validateConfig (D:\admin-project\guangxi-quan-vue3\node_modules\app-builder-lib\src\packager.ts:384:5) at Packager.build (D:\admin-project\guangxi-quan-vue3\node_modules\app-builder-lib\src\packager.ts:392:5) at executeFinally (D:\admin-project\guangxi-quan-vue3\node_modules\builder-util\src\promise.ts:12:14)
最新发布
06-08
**错误**：`ValidationError: options has unknown property &#39;signingHashAlgorithms&#39;` **原因**：electron-builder v23 后弃用了旧签名配置参数[^2]。 **修正方案**（更新 `package.json`）： ```json { ...
react之运行webpack报错：configuration.module has an unknown property 'loaders'
weixin_40200876的博客
07-27 649
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. - configuration.module has an unknown property 'loaders'. These properties...
【收藏】webpack configuration.module has an unknown property ‘loaders‘. These properties arevalid: 解决办法
学亮编程手记
08-02 695
https://blog.csdn.net/qq_34200501/article/details/85617651
- configuration.module has an unknown property ‘loader‘ 问题解决
mhx123456789的博客
06-20 186
- configuration.module has an unknown property 'loader' 问题解决
Js |webpack 使用loader时候 module里面存在loaders的版本问题！！
GC怪兽的Blog
02-08 3135
webpack.config.js module.exports = { entry: "./index.js", output: { path: __dirname, filename: "bundle.js" }, module: { loaders: [ { test: /\.css$/,...
webpack局部安装、配置与使用时的报错记录与解决方案
weixin_67665876的博客
11-08 3561
新手webpack配置时，容易遇到的Bug合集。
因webpack版本引起的系列报错问题
qq_49490164的博客
06-08 5582
前言：项目昨天还好好的运行，今天打开一堆报错，还不是npm install XXX能解决的（小声骂骂咧咧）报错： 查了很多资料发现是因为webpack版本引起的，在webpack5中移除了nodejs核心模块的polyfill自动引入，具体可查看这篇文章下面说说解决方法有缺就有补，没有自动引用就手动引用，先 然后我就发现我没有webpack.config.js文件了，因为vue脚手架3把这个文件封装到内部了， 但是可以在vue.config.js内调整webpack配置和我情况差不多的可以在 modul
configuration has an unknown property ‘Plugins‘. These properties are valid:
m0_56001619的博客
07-11 343
将Plugins改为plugins小写。
webpack之module.rules
richest_qi的博客
04-22 1万+
AMD是require.js在推广过程中对模块定义的规范化产出； CMD是sea.js在推广过程中对模块定义的规范化产出。 它们都是为了实现js在浏览器端的模块化开发，且异步加载。 其中，require.js中有全局require和局部require，而sea.js中只有局部require。 本文主要是为了记录下二者的使用，便于日后回忆使用
使用 webpack 搭建 vue 开发环境（二）
Jioho的博客
09-27 671
使用 webpack 搭建 vue 开发环境（二） 接着上一回，第二篇文章开始更进一步的配置 老规矩，基于 v0.0.1 的代码继续开发，这次配置结束后的代码将会划分为 v0.0.2 使用 less 完善开发体验 安装使用 css 预处理器-less npm install --save-dev less less-loader 修改配置，因为 test 是可以接收正则表达式的，那么对于 css和less的匹配，我们可以这样写：test: /\.(less|css)$/, webpack.base.js
⨯ Invalid configuration object. electron-builder 23.6.0 has been initialized using a configuration object that does not match the API schema. - configuration.win has an unknown property &#39;background&#39;. These properties are valid:
06-10
这是一个错误提示，似乎是在使用electron-builder进行打包时出现的问题。提示中指出，configuration.win中使用了一个未知的属性&#39;background&#39;。根据提示中指出的有效属性，可以检查一下配置文件是否符合API schema。可以尝试删除&#39;background&#39;属性，看看是否能够解决问题。另外，也可以检查一下electron-builder的版本是否正确，是否需要更新。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值