WARN "css.modules" option in vue.config.js is deprecated now, please use "css.requireModuleExtension" instead. INFO Starting development server... 98% after emitting CopyPlugin WARNING Compiled with 17 warnings 09:43:57 warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'computed' was not found in 'vue' warning in ./src/router/index.js "export 'default' (imported as 'VueRouter') was not found in 'vue-router' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'defineComponent' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'getCurrentInstance' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'h' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'inject' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'nextTick' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'onActivated' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'onDeactivated' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'onUnmounted' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'provide' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'reactive' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'ref' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'shallowRef' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'unref' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'watch' was not found in 'vue' warning in ./node_modules/vue-router/dist/vue-router.mjs "export 'watchEffect' was not found in 'vue'这个报错因为什么

时间: 2024-04-21 22:26:37 浏览: 367
这个报错是因为在使用Vue Router时,导入的Vue Router版本与当前项目中的Vue版本不匹配导致的。具体来说,Vue Router中使用了Vue 3的语法而当前项目中使用的是Vue 2,所以会出现一些语法上的错误。解决方法是将Vue Router更新到与当前项目中使用的Vue版本相匹配的版本。
相关问题

cross-env NODE_ENV=production nuxt build [warn] `mode` option is deprecated. You can safely remove it from `nuxt.config` [warn] vendor has been deprecated due to webpack4 optimization [warn] build.extractCSS.allChunks has no effect from v2.0.0. Please use build.optimization.splitChunks settings instead.

这是一个 Nuxt.js 的警告信息,提示你一些配置已经被废弃或者修改了。具体来说: - `mode` 选项已经被废弃了,你可以直接移除它。 - `vendor` 配置也被废弃了,因为 Webpack4 已经做了优化,你可以考虑移除它并使用默认的配置。 - `build.extractCSS.allChunks` 配置从 v2.0.0 开始不再生效,你可以使用 `build.optimization.splitChunks` 代替。 如果你想消除这些警告,可以按照提示修改你的 Nuxt.js 配置文件。

D:\jiankang\client_home>npm run serve > [email protected] serve > vue-cli-service serve Browserslist: caniuse-lite is outdated. Please run: npx update-browserslist-db@latest Why you should do it regularly: https://github.com/browserslist/update-db#readme INFO Starting development server... WARN A new version of sass-loader is available. Please upgrade for best experience. 98% after emitting CopyPlugin WARNING Compiled with 1 warning 下午8:53:47 warning in ./src/views/user/collect.vue?vue&type=style&index=0&id=c78b4e00&scoped=true&lang=css& Module Warning (from ./node_modules/postcss-loader/src/index.js): Warning (9:3) start value has mixed support, consider using flex-start instead @ ./node_modules/vue-style-loader??ref--7-oneOf-1-0!./node_modules/css-loader/dist/cjs.js??ref--7-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--7-oneOf-1-2!./node_modules/cache-loader/dist/cjs.js??ref--1-0!./node_modules/vue-loader/lib??vue-loader-options!./src/views/user/collect.vue?vue&type=style&index=0&id=c78b4e00&scoped=true&lang=css& 4:14-415 15:3-20:5 16:22-423 @ ./src/views/user/collect.vue?vue&type=style&index=0&id=c78b4e00&scoped=true&lang=css& @ ./src/views/user/collect.vue @ ./src/router/index.js @ ./src/main.js @ multi (webpack)-dev-server/client?http://10.148.12.80:8081&sockPath=/sockjs-node (webpack)/hot/dev-server.js ./src/main.js App running at: - Local: http://localhost:8081/ - Network: http://10.148.12.80:8081/ Note that the development build is not optimized. To create a production build, run npm run build. 怎么解决

<think>好的,我现在需要解决用户提到的Vue项目中sass-loader版本过旧以及postcss-loader的兼容性警告问题。首先,我应该回忆一下如何升级npm包,尤其是针对Vue CLI项目。记得Vue CLI通常会把webpack相关的loader放在devDependencies里,所以应该通过npm或者yarn来升级这些包。 首先,用户提到要升级sass-loader到最新版本。我需要确认当前sass-loader的最新版本是什么,可能需要查看npm官网或者通过npm info sass-loader来获取。不过用户可能只需要知道升级命令,比如运行npm install sass-loader@latest --save-dev。但需要注意与node-sass或dart-sass的兼容性,可能需要同时升级这些依赖。不过现在Vue CLI默认使用dart-sass,所以或许用户已经使用了它,但还是要提醒一下。 接下来是postcss-loader的警告,关于start值的兼容性。这可能是因为postcss-loader的配置中使用了过时的选项。PostCSS 8+可能会有一些变化,比如插件需要单独引入,或者配置方式不同。需要检查项目中的postcss.config.js文件,查看是否有使用过时的语法。另外,可能需要升级postcss本身到最新版本,以及相关的插件,比如autoprefixer。 另外,用户使用的是Vue CLI项目,可能vue.config.js中有相关的webpack配置覆盖,需要确认是否手动修改过postcss-loader的配置。如果没有,Vue CLI默认会处理这些配置,但升级相关依赖可能会解决问题。 还需要考虑是否需要清除npm缓存,或者删除node_modules和package-lock.json后重新安装依赖,以确保所有包都正确更新。 同时,用户可能遇到升级后的兼容性问题,比如某些语法不再支持,这时候需要查看sass-loader的迁移指南,或者postcss的更新日志,看看是否有破坏性变更。例如,sass-loader从v10到v11可能需要调整webpack的配置,或者使用额外的插件。 最后,生成相关问题的时候,应该围绕升级后的步骤、常见错误、配置调整和HMR相关的问题来展开,帮助用户进一步解决可能遇到的问题。</think>### 解决Vue项目中sass-loader升级与postcss警告问题 #### 步骤一:升级sass-loader至最新版本 1. **通过npm升级** 在项目根目录执行以下命令: ```bash npm install sass-loader@latest --save-dev ``` 若使用yarn: ```bash yarn add sass-loader@latest --dev ``` **注意**: - 确保同时升级`sass`(dart-sass)依赖,避免版本冲突: ```bash npm install sass@latest --save-dev ``` - Vue CLI默认使用`dart-sass`[^2],若项目未显式声明`sass`,需手动添加。 2. **验证升级结果** 检查`package.json`中版本号是否为最新: ```json "devDependencies": { "sass-loader": "^13.3.2", // 示例版本 "sass": "^1.63.6" } ``` --- #### 步骤二:修复postcss-loader兼容性警告 1. **升级postcss相关依赖** 运行命令更新核心包: ```bash npm install postcss postcss-loader autoprefixer --save-dev ``` 或指定版本: ```bash npm install [email protected] [email protected] [email protected] --save-dev ``` 2. **调整postcss配置** 在`postcss.config.js`中明确插件兼容性配置: ```javascript module.exports = { plugins: { 'autoprefixer': { overrideBrowserslist: ['> 1%', 'last 2 versions'] } } } ``` **关键点**: - 避免使用`start`等过时配置项,改用`overrideBrowserslist`[^1]。 - 确保配置语法兼容PostCSS 8+。 --- #### 步骤三:清理缓存并重启 1. **删除旧依赖与缓存** ```bash rm -rf node_modules package-lock.json npm cache clean --force npm install ``` 2. **重启开发服务器** ```bash npm run serve ``` --- #### 常见问题排查 - **场景1**:升级后出现Sass语法错误 **解决**:检查是否遗漏`sass`升级,或尝试在`vue.config.js`中显式指定实现: ```javascript module.exports = { css: { loaderOptions: { sass: { implementation: require('sass') } } } } ``` - **场景2**:PostCSS警告未消失 **解决**:检查浏览器兼容性配置是否被其他文件覆盖,如`.browserslistrc`需保持与`postcss.config.js`一致[^1]。 ---
阅读全文

相关推荐

npm WARN deprecated @stylelint/[email protected]: Use the original unforked package instead: postcss-markdown npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address' npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm WARN deprecated [email protected]: This package is deprecated. Use https://socket.dev/npm/package/eta instead. npm WARN deprecated [email protected]: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained npm WARN deprecated [email protected]: This module is no longer supported. npm WARN deprecated [email protected]: This package is no longer supported. npm WARN deprecated [email protected]: Upgrade to fsevents v2 to mitigate potential security issues npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated [email protected]: This package is no longer supported. npm WARN deprecated [email protected]: This package is no longer supported. npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated

npm warn old lockfile npm warn old lockfile The package-lock.json file was created with an old version of npm, npm warn old lockfile so supplemental metadata must be fetched from the registry. npm warn old lockfile npm warn old lockfile This is a one-time fix-up, please be patient... npm warn old lockfile npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410 npm warn deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. npm warn deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm warn deprecated [email protected]: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details. npm warn deprecated [email protected]: Node Sass is no longer supported. Please use sass or sass-embedded instead. npm warn deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. ⠸ PS G:\ChildrenBooks\springboot6kt9q920\src\main\resources\admin\admin> * 还原的历史记录 npm error path G:\ChildrenBooks\springboot6kt9q920\src\main\resources\package.json npm error errno -4058 npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open 'G:\ChildrenBooks\

C:\Users\HP>npm install -g @vue/cli npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm warn deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm warn deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead. npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: The apollo-server-errors package is part of Apollo Server v2 and v3, which are now end-of-life (as of October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more detail

npm ERR! code 1 npm ERR! git dep preparation failed npm ERR! command D:\Program Files\nodejs\node.exe D:\node\nodejs\node_global\node_modules\npm\bin\npm-cli.js install --force --cache=D:\Program Files\nodejs\node_cache --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run npm ERR! npm WARN using --force Recommended protections disabled. npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm ERR! npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs npm ERR! npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm ERR! npm WARN deprecated [email protected]: This package is deprecated. Use require('node:util').isDeepStrictEqual instead. npm ERR! npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm ERR! npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: This module is no longer supported. npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm ERR! npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm ERR! npm WARN deprecated [email protected]: this library is no longer supported npm ERR! npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm ERR! npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported npm ERR! npm WARN deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm ERR! npm WARN deprecated npm ERR! npm WARN deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm ERR! npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported npm ERR! npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead npm ERR! npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm ERR! npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: 3.x is no longer supported npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address' npm ERR! npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. npm ERR! npm WARN deprecated @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information. npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm ERR! npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm ERR! npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm ERR! npm WARN deprecated [email protected]: This package is no longer supported. npm ERR! npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm ERR! npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi' npm ERR! npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. npm ERR! npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm ERR! npm WARN deprecated [email protected]: The zlib module provides APIs for brotli compression/decompression starting with Node.js v10.16.0, please use it over iltorb npm ERR! npm WARN deprecated [email protected]: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details. npm ERR! npm WARN deprecated [email protected]: Node Sass is no longer supported. Please use sass or sass-embedded instead. npm ERR! npm WARN deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options. npm ERR! npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, fea ture detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm ERR! npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, fea ture detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm ERR! npm WARN cleanup Failed to remove some directories [ npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\mozjpeg', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\mozjpeg'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\mozjpeg' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\optipng-bin', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\optipng-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\optipng-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\cwebp-bin', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\cwebp-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\cwebp-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\gifsicle', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\gifsicle'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\gifsicle' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\pngquant-bin', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\pngquant-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\pngquant-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules', npm ERR! npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\cwebp-bin'] { npm ERR! npm WARN cleanup errno: -4082, npm ERR! npm WARN cleanup code: 'EBUSY', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\cwebp-bin' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ], npm ERR! npm WARN cleanup [ npm ERR! npm WARN cleanup 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\@babel\\polyfill', npm ERR! npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\@babel\polyfill'] { npm ERR! npm WARN cleanup errno: -4048, npm ERR! npm WARN cleanup code: 'EPERM', npm ERR! npm WARN cleanup syscall: 'rmdir', npm ERR! npm WARN cleanup path: 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\@babel\\polyfill' npm ERR! npm WARN cleanup } npm ERR! npm WARN cleanup ] npm ERR! npm WARN cleanup ] npm ERR! npm ERR! code 1 npm ERR! npm ERR! path D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass npm ERR! npm ERR! command failed npm ERR! npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js npm ERR! npm ERR! Building: D:\Program Files\nodejs\node.exe D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= npm ERR! npm ERR! �ڴ˽��������һ������һ����Ŀ����Ҫ���ò������ɣ������ӡ�/m�����ء� npm ERR! npm ERR! ��������ʱ��Ϊ 2025/5/27 15:48:02�� npm ERR! npm ERR! �ڵ� 1 �ϵ���Ŀ��D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln��(Ĭ��Ŀ��)�� npm ERR! npm ERR! ValidateSolutionConfiguration: npm ERR! npm ERR! �������ɽ���������á�Release|x64���� npm ERR! npm ERR! MSBUILD : error MSB3428: δ�ܼ��� Visual C++ �����VCBuild.exe����Ҫ��������⣬1) ��װ .NET Framework 2.0 SDK��2) ��װ Microsoft Visual Studio 2005���� 3) ������������װ��������λ�ã��뽫��λ�����ӵ�ϵͳ·���С� [D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln] npm ERR! npm ERR! �����������Ŀ��D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln��(Ĭ��Ŀ��)�IJ��� - ʧ�ܡ� npm ERR! npm ERR! npm ERR! npm ERR! ����ʧ�ܡ� npm ERR! npm ERR! npm ERR! npm ERR! ��D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln��(Ĭ��Ŀ��) (1) -> npm ERR! npm ERR! (_src_\libsass Ŀ��) -> npm ERR! npm ERR! MSBUILD : error MSB3428: δ�ܼ��� Visual C++ �����VCBuild.exe����Ҫ��������⣬1) ��װ .NET Framework 2.0 SDK��2) ��װ Microsoft Visual Studio 2005���� 3) ������������װ��������λ�ã��뽫��λ�����ӵ�ϵͳ·���С� [D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\binding.sln] npm ERR! npm ERR! npm ERR! npm ERR! 0 ������ npm ERR! npm ERR! 1 ������ npm ERR! npm ERR! npm ERR! npm ERR! ����ʱ�� 00:00:00.40 npm ERR! npm ERR! gyp info it worked if it ends with ok npm ERR! npm ERR! gyp verb cli [ npm ERR! npm ERR! gyp verb cli 'D:\\Program Files\\nodejs\\node.exe', npm ERR! npm ERR! gyp verb cli 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\bin\\node-gyp.js', npm ERR! npm ERR! gyp verb cli 'rebuild', npm ERR! npm ERR! gyp verb cli '--verbose', npm ERR! npm ERR! gyp verb cli '--libsass_ext=', npm ERR! npm ERR! gyp verb cli '--libsass_cflags=', npm ERR! npm ERR! gyp verb cli '--libsass_ldflags=', npm ERR! npm ERR! gyp verb cli '--libsass_library=' npm ERR! npm ERR! gyp verb cli ] npm ERR! npm ERR! gyp info using [email protected] npm ERR! npm ERR! gyp info using [email protected] | win32 | x64 npm ERR! npm ERR! gyp verb command rebuild [] npm ERR! npm ERR! gyp verb command clean [] npm ERR! npm ERR! gyp verb clean removing "build" directory npm ERR! npm ERR! gyp verb command configure [] npm ERR! npm ERR! gyp verb check python checking for Python executable "python2" in the PATH npm ERR! npm ERR! gyp verb which failed Error: not found: python2 npm ERR! npm ERR! gyp verb which failed at getNotFoundError (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:13:12) npm ERR! npm ERR! gyp verb which failed at F (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:68:19) npm ERR! npm ERR! gyp verb which failed at E (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:80:29) npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:89:16 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\index.js:42:5 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\windows.js:36:5 npm ERR! npm ERR! gyp verb which failed at FSReqCallback.oncomplete (fs.js:192:21) npm ERR! npm ERR! gyp verb which failed python2 Error: not found: python2 npm ERR! npm ERR! gyp verb which failed at getNotFoundError (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:13:12) npm ERR! npm ERR! gyp verb which failed at F (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:68:19) npm ERR! npm ERR! gyp verb which failed at E (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:80:29) npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\node_modules\which\which.js:89:16 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\index.js:42:5 npm ERR! npm ERR! gyp verb which failed at D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\isexe\windows.js:36:5 npm ERR! npm ERR! gyp verb which failed at FSReqCallback.oncomplete (fs.js:192:21) { npm ERR! npm ERR! gyp verb which failed code: 'ENOENT' npm ERR! npm ERR! gyp verb which failed } npm ERR! npm ERR! gyp verb check python checking for Python executable "python" in the PATH npm ERR! npm ERR! gyp verb which succeeded python D:\Python27\python.EXE npm ERR! npm ERR! gyp verb check python version D:\Python27\python.EXE -c "import sys; print "2.7.0 npm ERR! npm ERR! gyp verb check python version .%s.%s" % sys.version_info[:3];" returned: %j npm ERR! npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 14.20.0 npm ERR! npm ERR! gyp verb command install [ '14.20.0' ] npm ERR! npm ERR! gyp verb install input version string "14.20.0" npm ERR! npm ERR! gyp verb install installing version: 14.20.0 npm ERR! npm ERR! gyp verb install --ensure was passed, so won't reinstall if already installed npm ERR! npm ERR! gyp verb install version is already installed, need to check "installVersion" npm ERR! npm ERR! gyp verb got "installVersion" 9 npm ERR! npm ERR! gyp verb needs "installVersion" 9 npm ERR! npm ERR! gyp verb install version is good npm ERR! npm ERR! gyp verb get node dir target node version installed: 14.20.0 npm ERR! npm ERR! gyp verb build dir attempting to create "build" dir: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build npm ERR! npm ERR! gyp verb build dir "build" dir needed to be created? D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build npm ERR! npm ERR! gyp verb Not using VS2017: Could not use PowerShell to find VS2017 npm ERR! npm ERR! gyp verb build/config.gypi creating config file npm ERR! npm ERR! gyp verb build/config.gypi writing out config file: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\build\config.gypi npm ERR! npm ERR! gyp verb config.gypi checking for gypi file: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\config.gypi npm ERR! npm ERR! gyp verb common.gypi checking for gypi file: D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass\common.gypi npm ERR! npm ERR! gyp verb gyp gyp format was not specified; forcing "msvs" npm ERR! npm ERR! gyp info spawn D:\Python27\python.EXE npm ERR! npm ERR! gyp info spawn args [ npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\gyp\\gyp_main.py', npm ERR! npm ERR! gyp info spawn args 'binding.gyp', npm ERR! npm ERR! gyp info spawn args '-f', npm ERR! npm ERR! gyp info spawn args 'msvs', npm ERR! npm ERR! gyp info spawn args '-G', npm ERR! npm ERR! gyp info spawn args 'msvs_version=auto', npm ERR! npm ERR! gyp info spawn args '-I', npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-sass\\build\\config.gypi', npm ERR! npm ERR! gyp info spawn args '-I', npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\addon.gypi', npm ERR! npm ERR! gyp info spawn args '-I', npm ERR! npm ERR! gyp info spawn args 'C:\\Users\\23969\\.node-gyp\\14.20.0\\include\\node\\common.gypi', npm ERR! npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! npm ERR! gyp info spawn args '-Dnode_root_dir=C:\\Users\\23969\\.node-gyp\\14.20.0', npm ERR! npm ERR! gyp info spawn args '-Dnode_gyp_dir=D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp', npm ERR! npm ERR! gyp info spawn args '-Dnode_lib_file=C:\\Users\\23969\\.node-gyp\\14.20.0\\<(target_arch)\\node.lib', npm ERR! npm ERR! gyp info spawn args '-Dmodule_root_dir=D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-sass', npm ERR! npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! npm ERR! gyp info spawn args '--depth=.', npm ERR! npm ERR! gyp info spawn args '--no-parallel', npm ERR! npm ERR! gyp info spawn args '--generator-output', npm ERR! npm ERR! gyp info spawn args 'D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-sass\\build', npm ERR! npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! npm ERR! gyp info spawn args ] npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! Warning: unrecognized setting VCCLCompilerTool/MultiProcessorCompilation npm ERR! npm ERR! gyp verb command build [] npm ERR! npm ERR! gyp verb build type Release npm ERR! npm ERR! gyp verb architecture x64 npm ERR! npm ERR! gyp verb node dev dir C:\Users\23969\.node-gyp\14.20.0 npm ERR! npm ERR! gyp verb found first Solution file build/binding.sln npm ERR! npm ERR! gyp verb could not find "msbuild.exe" in PATH - finding location in registry npm ERR! npm ERR! gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe npm ERR! npm ERR! gyp info spawn args [ npm ERR! npm ERR! gyp info spawn args 'build/binding.sln', npm ERR! npm ERR! gyp info spawn args '/nologo', npm ERR! npm ERR! gyp info spawn args '/p:Configuration=Release;Platform=x64' npm ERR! npm ERR! gyp info spawn args ] npm ERR! npm ERR! gyp ERR! build error npm ERR! npm ERR! gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1 npm ERR! npm ERR! gyp ERR! stack at ChildProcess.onExit (D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-gyp\lib\build.js:262:23) npm ERR! npm ERR! gyp ERR! stack at ChildProcess.emit (events.js:400:28) npm ERR! npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:285:12) npm ERR! npm ERR! gyp ERR! System Windows_NT 10.0.26100 npm ERR! npm ERR! gyp ERR! command "D:\\Program Files\\nodejs\\node.exe" "D:\\Program Files\\nodejs\\node_cache\\_cacache\\tmp\\git-cloneuwf27x\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" npm ERR! npm ERR! gyp ERR! cwd D:\Program Files\nodejs\node_cache\_cacache\tmp\git-cloneuwf27x\node_modules\node-sass npm ERR! npm ERR! gyp ERR! node -v v14.20.0 npm ERR! npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! npm ERR! gyp ERR! not ok npm ERR! npm ERR! Build failed with error code: 1

C:\Windows\System32>npm install -g @vue/cli --force npm warn using --force Recommended protections disabled. npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm warn deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead. npm warn deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: The apollo-datasource package is part of Apollo Server v2 and v3, which are now end-of-life (as of October 22nd 2023 and October 22nd 2024, respectively). See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details. npm warn deprecated [email protected]: The apollo-server-errors package is part of Apollo Server v2 and v3, which are now end-of-life (as of October 22nd 2023 and October 22nd 2024, respec

npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: [email protected] npm WARN node_modules/eslint npm WARN dev eslint@"7.15.0" from the root project npm WARN 4 more (@vue/cli-plugin-eslint, babel-eslint, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer eslint@">= 1.6.0" from @vue/[email protected] npm WARN node_modules/@vue/cli-plugin-eslint npm WARN dev @vue/cli-plugin-eslint@"4.4.6" from the root project npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: [email protected] npm WARN node_modules/eslint npm WARN dev eslint@"7.15.0" from the root project npm WARN 4 more (@vue/cli-plugin-eslint, babel-eslint, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer eslint@">= 4.12.1" from [email protected] npm WARN node_modules/babel-eslint npm WARN dev babel-eslint@"10.1.0" from the root project npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: [email protected] npm WARN node_modules/eslint npm WARN dev eslint@"7.15.0" from the root project npm WARN 4 more (@vue/cli-plugin-eslint, babel-eslint, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer eslint@"^6.2.0 || ^7.0.0" from [email protected] npm WARN node_modules/eslint-plugin-vue npm WARN dev eslint-plugin-vue@"7.2.0" from the root project npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: eslint@undefined npm WARN node_modules/eslint npm WARN dev eslint@"7.15.0" from the root project npm WARN npm WARN Could not resolve dependency: npm WARN peer eslint@">=1.6.0 <7.0.0" from [email protected] npm WARN node_modules/@vue/cli-plugin-eslint/node_modules/eslint-loader npm WARN eslint-loader@"^2.2.1" from @vue/[email protected] npm WARN node_modules/@vue/cli-plugin-eslint npm ERR! code ENOTFOUND npm ERR! syscall getaddrinfo npm ERR! errno ENOTFOUND npm ERR! network request to http://registry.cnpmjs.org/eslint failed, reason: getaddrinfo ENOTFOUND registry.cnpmjs.org npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! A complete log of this run can be found in: npm ERR! D:\Nodejs\node_cache\_logs\2023-06-05T01_57_35_554Z-debug-0.log

npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm WARN deprecated [email protected]: This loader has been deprecated. Please use eslint-webpack-plugin npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated [email protected]: this library is no longer supported npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated [email protected]: 3.x is no longer supported npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address' npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi' npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. added 1400 packages in 1m

npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/mas-creator-admin - Not found npm ERR! 404 npm ERR! 404 '[email protected]' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url. npm ERR! A complete log of this run can be found in: npm ERR! D:\nodejs\node_cache\_logs\2025-03-07T18_08_37_097Z-debug-0.log PS D:\zuoye\yimiao\client> npm install --save-dev @vue/cli-service npm WARN config global --global, --local are deprecated. Use --location=global instead. npm WARN deprecated [email protected]: This package is no longer supported. npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it . Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm WARN deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm WARN deprecated [email protected]: This package is no longer supported. npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated [email protected]: This package is no longer supported. npm WARN deprecated [email protected]: This package is no longer supported. npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm WARN deprecated [email protected]: This module is no longer supported. npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported o

C:\Users\MI\Desktop\毕业设计\luckysheet_import_export-master>npm install npm warn old lockfile npm warn old lockfile The package-lock.json file was created with an old version of npm, npm warn old lockfile so supplemental metadata must be fetched from the registry. npm warn old lockfile npm warn old lockfile This is a one-time fix-up, please be patient... npm warn old lockfile npm warn deprecated [email protected]: Please upgrade to v0.1.5 npm warn deprecated [email protected]: Please upgrade to v0.1.7 npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated [email protected]: Please update to ini >=1.3.6 to avoid a prototype pollution issue npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: Please upgrade to v1.0.1 npm warn deprecated [email protected]: This package is deprecated. Use https://socket.dev/npm/package/eta instead. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead. npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transfor

最新推荐

recommend-type

170: Warning: (1681, ‘Integer display width is deprecated and will be removed in a future release.’)

在Python的数据库操作中,尤其是当你使用pymysql库连接MySQL数据库时,可能会遇到一个警告,提示"Integer display width is deprecated and will be removed in a future release." 这个警告源于MySQL数据库的一个...
recommend-type

全面掌握Oracle9i:基础教程与实践指南

Oracle9i是一款由甲骨文公司开发的关系型数据库管理系统,它在信息技术领域中占据着重要的地位。Oracle9i的“i”代表了互联网(internet),意味着它具有强大的网络功能,能够支持大规模的网络应用。该系统具有高度的数据完整性和安全性,并且其强大稳定的特点使得它成为了企业级应用的首选数据库平台。 为了全面掌握Oracle9i,本教程将从以下几个方面详细讲解: 1. Oracle9i的安装与配置:在开始学习之前,您需要了解如何在不同的操作系统上安装Oracle9i数据库,并对数据库进行基本的配置。这包括数据库实例的创建、网络配置文件的设置(如listener.ora和tnsnames.ora)以及初始参数文件的设置。 2. SQL语言基础:SQL(Structured Query Language)是用于管理和操作关系型数据库的标准语言。您需要熟悉SQL语言的基本语法,包括数据查询语言(DQL)、数据操纵语言(DML)、数据定义语言(DDL)和数据控制语言(DCL)。 3. PL/SQL编程:PL/SQL是Oracle公司提供的过程化语言,它是SQL的扩展,增加了过程化编程的能力。学习PL/SQL可以让您编写更复杂、更高效的数据库程序,包括存储过程、函数、包和触发器等。 4. Oracle9i的数据管理:这部分内容涉及数据表的创建、修改、删除以及索引、视图、同义词、序列和分区等高级特性。 5. 数据库性能优化:为了确保数据库的高效运行,需要对数据库进行性能调优。这包括了解Oracle9i的内存管理、锁定机制、SQL语句优化和数据库设计原则等。 6. 数据库备份与恢复:为防止数据丢失或损坏,需要了解Oracle9i的备份和恢复机制。您将学习到如何使用RMAN(Recovery Manager)进行数据备份和恢复,并且熟悉数据库的逻辑备份和恢复策略。 7. 安全管理:安全管理是保护数据库不受非法访问和操作的重要环节。Oracle9i提供了丰富的安全特性,如用户权限管理、审计和加密等,您需要学习如何实施这些安全措施来保证数据库的安全性。 8. Oracle9i网络管理:由于Oracle9i对网络的特别设计,您还需要掌握如何管理Oracle网络,包括监听器的配置、网络故障的诊断等。 9. 高级特性介绍:Oracle9i提供了很多高级功能,如高级复制、流复制、高级安全性、Oracle Data Guard等,这些内容将帮助您掌握Oracle9i的高级特性,从而在面对复杂业务需求时有更多解决方案。 在学习Oracle9i教程的过程中,您将通过大量实例练习加深理解,同时也会了解到最佳实践和常见问题的解决方法。本教程的目的是让您全面掌握Oracle9i数据库管理系统的使用,并具备解决实际问题的能力,无论您是数据库管理员、开发人员还是系统分析师,本教程都将成为您提升技能的有力工具。
recommend-type

【数据融合技术】:甘肃土壤类型空间分析中的专业性应用

# 摘要 数据融合技术作为一种集成多源数据信息的方法,在土壤类型空间分析中发挥着关键作用。本文介绍了数据融合技术的基本概念及其理论基础,阐述了数据预处理、同步整合及冲突解决等关键技术,并详细描述了甘肃土壤类型数据准备的流程,包括数据采集、质量评估、空间化处理及融合实践准备。通过具体案例分析,展示了数据融合在土壤类型空间分布分析、土壤质量评估及土壤保护规划中的应用。同时,文
recommend-type

模糊大津法

<think>首先,用户查询是关于“模糊大津法”的,我需要理解这个术语。从引用中,我知道大津法(Otsu's method)是一种图像二值化的全局阈值算法。用户提到“模糊大津法”,这可能是大津法与模糊理论结合的一种变体。我需要基于提供的引用和自己的知识来回答。关键引用:- [^1]:讨论了大津法在图像处理中的应用,特别是二值化。- [^2]:解释了大津法的原理和实现。- [^3]:提到大津法是全局阈值算法。- [^4]:讨论了高斯模糊对大津二值化算法的影响,指出高斯模糊可以减少噪声,提高阈值计算的准确性。用户的问题是:“我想查找关于模糊大津法的技术资料或实现方法请问模糊大津法原理实现方法技术文
recommend-type

SOA服务设计原则:2007年7月版原理深入解析

由于提供的文件信息是相同的标题、描述和标签,且压缩包中仅包含一个文件,我们可以得出文件“Prentice.Hall.SOA.Principles.of.Service.Design.Jul.2007.pdf”很可能是一本关于面向服务架构(SOA)的书籍。该文件的名称和描述表明了它是一本专门讨论服务设计原则的出版物,其出版日期为2007年7月。以下是从标题和描述中提取的知识点: ### SOA设计原则 1. **服务导向架构(SOA)基础**: - SOA是一种设计原则,它将业务操作封装为可以重用的服务。 - 服务是独立的、松耦合的业务功能,可以在不同的应用程序中复用。 2. **服务设计**: - 设计优质服务对于构建成功的SOA至关重要。 - 设计过程中需要考虑到服务的粒度、服务的生命周期管理、服务接口定义等。 3. **服务重用**: - 服务设计的目的是为了重用,需要识别出业务领域中可重用的功能单元。 - 通过重用现有的服务,可以降低开发成本,缩短开发时间,并提高系统的整体效率。 4. **服务的独立性与自治性**: - 服务需要在技术上是独立的,使得它们能够自主地运行和被管理。 - 自治性意味着服务能够独立于其他服务的存在和状态进行更新和维护。 5. **服务的可组合性**: - SOA强调服务的组合性,这意味着可以通过组合不同的服务构建新的业务功能。 - 服务之间的交互应当是标准化的,以确保不同服务间的无缝通信。 6. **服务的无状态性**: - 在设计服务时,最好让服务保持无状态,以便它们可以被缓存、扩展和并行处理。 - 状态信息可以放在服务外部,比如数据库或缓存系统中。 7. **服务的可发现性**: - 设计服务时,必须考虑服务的发现机制,以便服务消费者可以找到所需的服务。 - 通常通过服务注册中心来实现服务的动态发现和绑定。 8. **服务的标准化和协议**: - 服务应该基于开放标准构建,确保不同系统和服务之间能够交互。 - 服务之间交互所使用的协议应该广泛接受,如SOAP、REST等。 9. **服务的可治理性**: - 设计服务时还需要考虑服务的管理与监控,确保服务的质量和性能。 - 需要有机制来跟踪服务使用情况、服务变更管理以及服务质量保障。 10. **服务的业务与技术视角**: - 服务设计应该同时考虑业务和技术的视角,确保服务既满足业务需求也具备技术可行性。 - 业务规则和逻辑应该与服务实现逻辑分离,以保证业务的灵活性和可维护性。 ### SOA的实施挑战与最佳实践 1. **变更管理**: - 实施SOA时需要考虑到如何管理和适应快速变更。 - 必须建立适当的变更控制流程来管理和批准服务的更改。 2. **安全性**: - 安全是SOA设计中的一个关键方面,需要确保服务交互的安全。 - 需要实现身份验证、授权、加密和审计机制以保护数据和服务。 3. **互操作性**: - 服务应设计为可与不同平台和技术实现互操作。 - 必须确保服务之间可以跨平台和语言进行通信。 4. **质量保证**: - 对服务进行持续的质量监控和改进是实施SOA不可或缺的一部分。 - 服务质量(QoS)相关的特性如性能、可靠性、可用性等都应被纳入设计考量。 5. **投资回报(ROI)和成本效益分析**: - 从经济角度评估实施SOA的合理性。 - 在设计服务时考虑长期成本节约和ROI。 根据以上知识点的总结,可以看出“Prentice.Hall.SOA.Principles.of.Service.Design.Jul.2007.pdf”这本书很可能是系统地介绍SOA设计原则和最佳实践的专业著作,对于想要深入了解SOA设计的读者来说是一本宝贵的参考资料。
recommend-type

【空间分布规律】:甘肃土壤类型与农业生产的关联性研究

# 摘要 本文对甘肃土壤类型及其在农业生产中的作用进行了系统性研究。首先概述了甘肃土壤类型的基础理论,并探讨了土壤类型与农业生产的理论联系。通过GIS技术分析,本文详细阐述了甘肃土壤的空间分布规律,并对其特征和影响因素进行了深入分析。此外,本文还研究了甘肃土壤类型对农业生产实际影响,包括不同区域土壤改良和作物种植案例,以及土壤养分、水分管理对作物生长周期和产量的具体影响。最后,提出了促进甘肃土壤与农业可持续发展的策略,包括土壤保护、退化防治对策以及土壤类型优化与农业创新的结合。本文旨在为
recommend-type

rc滤波导致相位

<think>我们参考了关于RC滤波器的多个引用,特别是引用[3]和引用[4]中提到了相位的影响。 根据引用[3]:对于一阶RC低通滤波器,相位角θ的计算公式为:θ = -arctan(ωRC),其中ω是角频率(ω=2πf),R是电阻值,C是电容值。 引用[4]也解释了相位变化的原因:电容是储能元件,信号通过电容时会有延时,导致输出信号相对于输入信号产生相位差。 因此,对于RC低通滤波器,相位差是负的,表示输出信号滞后于输入信号。滞后的角度随频率增加而增加,在截止频率处滞后45度,当频率趋近于无穷大时,滞后90度。 对于RC高通滤波器,根据引用[3]的提示(虽然没有直接给出公式),
recommend-type

FTP搜索工具:IP检测与数据库管理功能详解

FTP(File Transfer Protocol)即文件传输协议,是一种用于在网络上进行文件传输的协议,使得用户可以通过互联网与其他用户进行文件共享。FTP Search是一款专注于FTP文件搜索的工具,其工作原理和应用场景使其在处理大规模数据共享和远程文件管理方面具有一定的优势。 **属性页控件** 属性页控件是一种用户界面元素,通常用于组织多个属性或设置页面。在FTP Search工具中,属性页控件可能被用来显示和管理FTP搜索的各项参数。用户可以通过它来设置搜索的FTP服务器地址、登录凭证、搜索范围以及结果处理方式等。属性页控件可以提高用户操作的便利性,使得复杂的设置更加直观易懂。 **Ping命令** Ping命令是互联网上广泛使用的一种网络诊断工具。它通过发送ICMP(Internet Control Message Protocol)回显请求消息到指定的IP地址,并等待接收回显应答,以此来检测目标主机是否可达以及网络延迟情况。在FTP Search工具中,Ping命令被用来检测FTP服务器的存活状态,即是否在线并能够响应网络请求。 **扫描主机端口** 端口扫描是网络安全领域中的一个基本操作,它用于检测特定主机上的哪些端口是开放的、关闭的或是被过滤的。了解端口的状态可以帮助确定目标主机上运行的服务和应用程序。在FTP Search工具中,端口扫描功能可能被用于识别FTP服务器上开放的端口,从而帮助用户找到合适的途径进行文件传输。 **数据库管理** 数据库管理在数据密集型应用中扮演着关键角色。FTP Search工具中包含的数据库操作功能,如打开、添加、查询和关闭数据库,表明该工具可能被设计为与数据库系统交互,以便更好地处理搜索到的FTP文件信息。可能涉及到的数据库管理系统(DBMS)包括MySQL、Microsoft SQL Server、SQLite等,用户可以通过工具提供的数据库管理接口来进行数据的维护和检索。 **IP地址控件** IP地址控件是一种用户界面组件,它允许用户输入或选择一个IP地址。在FTP Search工具中,IP地址控件用于输入目标FTP服务器的IP地址,使工具能够定位并连接到相应的服务器。该控件可能还具备验证IP地址有效性(如是否符合IPv4标准)的功能,并且能提供下拉列表或自动完成来提升用户体验。 综上所述,FTP Search工具是一个集成了多种网络和数据库操作功能的实用工具。通过属性页控件,用户可以方便地配置和管理工具;Ping命令和端口扫描功能则有助于用户确认服务器的状态和可用性;数据库管理功能则确保用户能够有效地存储和查询FTP搜索结果;而IP地址控件则简化了用户对服务器地址的输入流程。这些功能相互配合,使得FTP Search工具在执行FTP搜索任务时更加强大、高效和用户友好。对于网络管理员、数据分析师、IT专业人员等,这类工具能够显著提升工作效率,尤其是在处理大规模的文件共享和数据检索时。
recommend-type

【制图技术】:甘肃高质量土壤分布TIF图件的成图策略

# 摘要 本文针对甘肃土壤分布数据的TIF图件制作进行了系统研究。首先概述了甘肃土壤的分布情况,接着介绍了TIF图件的基础知识,包括其格式特点、空间数据表达以及质量控制方法。随后,文中构建了成图策略的理论框架,分析了土壤分布图的信息需求与数据处理流程,并探讨了成图原则与标准。在实践操作部分,详细阐述了制图软
recommend-type

iperf命令-t最多能设置多大

<think>首先,用户的问题是:“我想了解iperf命令中-t参数的最大可设置值 请问iperf -t parameter maximum value”。这涉及到iperf工具,具体是-t参数的最大值。 从系统指令中,我需要: - 使用$...$格式处理行内数学表达式。 - 独立公式用$$...$$格式。 - 使用中文回答。 - 生成相关问题。 - 在引用的段落末尾添加引用标识。 - 回答结构清晰,逐步解决问题。 参考提供的引用: - 引用[1]: 提到iperf3用于性能测试,但不是文件传输工具,因为UDP丢包可能导致文件长度不一致。使用方式:iperf3 -s -F ./log.tx