【產(chǎn)品名稱】：/ 多門店系統(tǒng)

【產(chǎn)品版本】：v3.3

view\admin  

直接安裝npm install 報(bào)以下錯(cuò)誤。

npm warn deprecated svgo@1.3.0: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm warn deprecated vue@2.6.10: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm warn deprecated vue@2.6.14: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
npm warn deprecated eslint@4.19.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn deprecated highlight.js@9.15.10: Version no longer supported. Upgrade to @latest
npm warn deprecated core-js@2.6.10: 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.
npm warn deprecated core-js-pure@3.20.2: core-js-pure@<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-pure.
npm error code ENOTFOUND
npm error syscall getaddrinfo
npm error errno ENOTFOUND
npm error network request to https://registry.nlark.com/sass-loader/download/sass-loader-11.1.1.tgz failed, reason: getaddrinfo ENOTFOUND registry.nlark.com
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly.  See: 'npm help config'
npm error A complete log of this run can be found in: C:\Users\1\AppData\Local\npm-cache\_logs\2025-10-28T02_18_25_259Z-debug-0.log