npm 下载依赖报错 npm ERR! SocksProxyAgent is not a constructor

最新推荐文章于 2025-10-16 16:00:00 发布
原创 最新推荐文章于 2025-10-16 16:00:00 发布 · 1.8k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#npm #vue.js #前端

当启动Vue项目并执行npm安装时遇到 socks5代理错误，可以通过检查和清除npm代理设置来解决。首先，使用`npm config get proxy`确认代理设置，然后用`npm config delete proxy`删除代理配置。执行这些步骤后，重新运行`npm install`即可成功安装依赖。

在启动 vue 项目执行npm 报错时

E:\demo>npm install
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
npm ERR! SocksProxyAgent is not a constructor

npm ERR! A complete log of this run can be found in:
npm ERR!     D:\node_cache\_logs\2022-08-19T03_05_44_154Z-debug-0.log

出现以上错误时不要慌，VPN就是在我的https-proxy上加了代理，导致npm安装不上依赖
查看代理

npm config get proxy

清理代理

npm config delete proxy

E:\demo>npm config get proxy
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.
socks5://10.181.39.200:7890

E:\demo>npm config delete proxy
npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead.

这会重新执行，就可以啦

npm install
shmilyhq
关注
simple-proxy-agent:通过HTTP和SOCKS代理发送HTTP和HTTPS流量的简单代理
04-28
简单代理 通过HTTP和SOCKS代理的HTTP和HTTPS的简单代理 目录 安装 npm install simple-proxy-agent 用法 代理请求 const fetch = require ( 'node-fetch' ) ; const ProxyAgent = require ( 'simple-proxy-agent' ) ; fetch ( 'https://example.com' , { agent : new ProxyAgent ( 'http://0.0.0.0:8080' , { // Options, with all defaults tunnel : true , // If true, will tunnel all HTTPS using CONNECT method timeout : 5000 , // Tim
node-proxy-agent:将代理协议映射到`http.Agent`实现
05-13
代理人 将代理协议映射到http.Agent实现 该模块提供了一个功能，可基于给定的代理URI返回代理http.Agent实例以供使用。 如果未提供URI，则使用从$HTTP_PROXY ， $HTTPS_PROXY和$NO_PROXY等获取URI。 使用LRU缓存，以便透明地将http.Agent实例重新用于对同一代理服务器的后续HTTP请求。 下表列出了当前实现的协议映射： 协议 http请求的代理 https请求的代理 例子 http http://proxy-server-over-tcp.com:3128 https https://proxy-server-over-tls.com:3129 socks(v5) socks://username:password@some-socks-proxy.com:9050 （用户名和密码是可选的） socks5 soc
Web3.providers.HttpProvider is not a constructor报错
and_what_not的博客
12-24 1216
自己也花了很多时间，其实就是版本的原因！我的web版本是4.3.0。只需要修改一步就可以了。这个是网上给出的代码，但是一直报错。
npm安装常见报错解决办法
最新发布
2401_84038155的博客
10-16 188
你可以尝试使用npm install --force或npm install --legacy-peer-deps来强制安装，尽管这可能会接受一些可能不正确的依赖解析。如果版本不匹配，你可能需要重新安装node和npm，或者使用一个版本管理工具，如nvm，来管理多个node版本。4.删除package-lock.json文件：如果错误与package-lock.json文件有关，你可以尝试删除这个文件，然后再次运行npm install。1.清除npm缓存：有时候，npm的缓存可能会导致安装失败。
node.js使用代理踩的坑最终的解决方案使用https和socks-proxy-agent解决
陈钇钇的博客
01-09 2707
/ ...这段代码定义了一个名为的函数，用于发起 HTTPS 请求。它利用 JavaScript 的Promise来处理异步操作，确保请求完成后再继续执行后续代码。options（请求配置）和body（请求体）。：创建一个新的 Promise 对象，用于处理异步操作。：发起 HTTPS 请求，其中options包含了请求的配置信息（如 URL、请求方法、头部等）。：当接收到数据块时触发，将数据块累加到字符串中。：当响应结束时触发，此时会解析 Promise，并返回完整的响应数据。
Webpack使用ReactHMR时出现SocketClient is not a constructor
陈梵的博客
03-30 1806
在学习使用Webpack进行ReactHMR的时候出现了一个问题。 Uncaught TypeError: SocketClient is not a constructor at initWDSSocket (build.js:2229:24) 网上搜了一堆，也没发现啥原因。stackoverflow有人说把@pmmmwh/react-refresh-webpack-plugin升级到最新的。去github上也看了，作者的原话是0.5.0-rc.4 should work with WDS v4 by
横向移动：Socks 代理 || 本地代理 技术.
网络安全领域___专研者.
06-12 8179
Socks 代理又称全能代理，就像有很多跳线的转接板，它只是简单地将一端的系统连接到另外一端。支持多种协议，包括http、ftp请求及其它类型的请求。它分socks 4 和socks 5两种类型，socks 4只支持TCP协议而socks 5支持TCP/UDP协议，还支持各种身份验证机制等协议。其标准端口为1080.
'vue-cli-service' 不是内部或外部命令，也不是可运行的程序 或批处理文件。 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! mas-creator-admin@0.1.0 serve: `vue-cli-service serve` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the mas-creator-admin@0.1.0 serve script. npm ERR! T
03-22
当遇到 `'vue-cli-service' is not recognized` 或者 `command not found` 的错误时，通常是因为 Vue CLI 工具或者项目中的某些配置存在问题。以下是可能的原因以及解决方案： #### 可能原因及对应解决方法 1. **...
npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@highcharts%2fpackedbubble - Not found npm ERR! 404 npm ERR! 404 '@highcharts/packedbubble@*' 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: C:\Users\wangx\AppData\Local\npm-cache\_logs\2025-04-27T02_12_59_444Z-debug-0.log 报错了
04-28
<Highcharts :options="options" constructor-type="chart" /> ``` ### 五、常见问题解决 1. **Node版本冲突**：若使用Node 18+出现SSL错误，添加环境变量： ```bash # Windows PowerShell $env:NODE_OPTIONS = ...
[root@localhost admin]# npm install --save core-js/modules/es.array.push.js \ > core-js/modules/es.array.reduce.js \ > core-js/modules/es.error.cause.js \ > core-js/modules/esnext.iterator.constructor.js \ > core-js/modules/esnext.iterator.map.js \ > core-js/modules/esnext.iterator.reduce.js npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /root/huasenjio-compose-master/huasen-frontend/admin/core-js/modules/es.array.push.js/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/root/huasenjio-compose-master/huasen-frontend/admin/core-js/modules/es.array.push.js/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2025-03-05T12_12_13_897Z-debug-0.log
03-11
`core-js/modules/...` 是 `core-js` 包内部的模块路径，但直接运行 `npm install --save core-js/modules/xxx.js` 时，npm 会误认为你要安装本地文件而非远程包，因此报错。 2. **依赖缺失** 项目可能依赖 `...
安装 报错npm WARN deprecated npmlog@4.1.2: This package is no longer supported. npm WARN deprecated are-we-there-yet@1.1.7: This package is no longer supported. npm WARN deprecated gauge@2.7.4: This package is no longer supported. npm ERR! code 1 npm ERR! path /Users/yangjia/workspace/company/dkYun/SDK2.0/node_modules/microtime npm ERR! command failed npm ERR! command sh -c prebuild-install || node-gyp rebuild npm ERR! CXX(target) Release/obj.target/microtime/src/microtime.o npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using node-gyp@8.4.1 npm ERR! gyp info using node@16.14.0 | darwin | arm64 npm ERR! gyp info find Python using Python version 3.12.1 found at "/Library/Frameworks/Python.framework/Versions/3.12/bin/python3" npm ERR! gyp info spawn /Library/Frameworks/Python.framework/Versions/3.12/bin/python3 npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py', npm ERR! gyp info spawn args 'binding.gyp', npm ERR! gyp info spawn args '-f', npm ERR! gyp info spawn args 'make', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/Users/yangjia/workspace/company/dkYun/SDK2.0/node_modules/microtime/build/config.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/common.gypi', npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! gyp info spawn args '-Dnode_root_dir=/Users/yangjia/Library/Caches/node-gyp/16.14.0', npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp', npm ERR! gyp info spawn args '-Dnode_lib_file=/Users/yangjia/Library/Caches/node-gyp/16.14.0/<(target_arch)/node.lib', npm ERR! gyp info spawn args '-Dmodule_root_dir=/Users/yangjia/workspace/company/dkYun/SDK2.0/node_modules/microtime', npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! gyp info spawn args '--depth=.', npm ERR! gyp info spawn args '--no-parallel', npm ERR! gyp info spawn args '--generator-output', npm ERR! gyp info spawn args 'build', npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! gyp info spawn args ] npm ERR! gyp info spawn make npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] npm ERR! In file included from ../src/microtime.cc:9: npm ERR! In file included from ../../nan/nan.h:222: npm ERR! In file included from ../../nan/nan_converters.h:67: npm ERR! ../../nan/nan_converters_43_inl.h:22:1: error: no viable conversion from 'Local<v8::Context>' to 'v8::Isolate *' npm ERR! X(Boolean) npm ERR! ^~~~~~~~~~ npm ERR! ../../nan/nan_converters_43_inl.h:18:23: note: expanded from macro 'X' npm ERR! val->To ## TYPE(isolate->GetCurrentContext()) \ npm ERR! ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:3086:37: note: passing argument to parameter 'isolate' here npm ERR! Local<Boolean> ToBoolean(Isolate* isolate) const; npm ERR! ^ npm ERR! In file included from ../src/microtime.cc:9: npm ERR! In file included from ../../nan/nan.h:222: npm ERR! In file included from ../../nan/nan_converters.h:67: npm ERR! ../../nan/nan_converters_43_inl.h:22:1: error: no member named 'FromMaybe' in 'v8::Local<v8::Boolean>' npm ERR! X(Boolean) npm ERR! ^~~~~~~~~~ npm ERR! ../../nan/nan_converters_43_inl.h:19:12: note: expanded from macro 'X' npm ERR! .FromMaybe(v8::Local<v8::TYPE>())); \ npm ERR! ^ npm ERR! ../../nan/nan_converters_43_inl.h:40:1: error: no viable conversion from 'Local<v8::Context>' to 'v8::Isolate *' npm ERR! X(bool, Boolean) npm ERR! ^~~~~~~~~~~~~~~~ npm ERR! ../../nan/nan_converters_43_inl.h:37:29: note: expanded from macro 'X' npm ERR! return val->NAME ## Value(isolate->GetCurrentContext()); \ npm ERR! ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:3096:30: note: passing argument to parameter 'isolate' here npm ERR! bool BooleanValue(Isolate* isolate) const; npm ERR! ^ npm ERR! In file included from ../src/microtime.cc:9: npm ERR! In file included from ../../nan/nan.h:222: npm ERR! In file included from ../../nan/nan_converters.h:67: npm ERR! ../../nan/nan_converters_43_inl.h:40:1: error: no viable conversion from returned value of type 'bool' to function return type 'imp::ToFactory<bool>::return_t' (aka 'Maybe<bool>') npm ERR! X(bool, Boolean) npm ERR! ^~~~~~~~~~~~~~~~ npm ERR! ../../nan/nan_converters_43_inl.h:37:10: note: expanded from macro 'X' npm ERR! return val->NAME ## Value(isolate->GetCurrentContext()); \ npm ERR! ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:10437:7: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'bool' to 'const v8::Maybe<bool> &' for 1st argument npm ERR! class Maybe { npm ERR! ^ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:10437:7: note: candidate constructor (the implicit move constructor) not viable: no known conversion from 'bool' to 'v8::Maybe<bool> &&' for 1st argument npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:10492:12: note: explicit constructor is not a candidate npm ERR! explicit Maybe(const T& t) : has_value_(true), value_(t) {} npm ERR! ^ npm ERR! In file included from ../src/microtime.cc:9: npm ERR! In file included from ../../nan/nan.h:223: npm ERR! In file included from ../../nan/nan_new.h:189: npm ERR! ../../nan/nan_implementation_12_inl.h:356:37: error: too few arguments to function call, expected 2, have 1 npm ERR! return v8::StringObject::New(value).As<v8::StringObject>(); npm ERR! ~~~~~~~~~~~~~~~~~~~~~ ^ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:6196:23: note: 'New' declared here npm ERR! static Local<Value> New(Isolate* isolate, Local<String> value); npm ERR! ^ npm ERR! In file included from ../src/microtime.cc:9: npm ERR! In file included from ../../nan/nan.h:2722: npm ERR! ../../nan/nan_object_wrap.h:24:25: error: no member named 'IsNearDeath' in 'Nan::Persistent<v8::Object>' npm ERR! assert(persistent().IsNearDeath()); npm ERR! ~~~~~~~~~~~~ ^ npm ERR! /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/assert.h:99:25: note: expanded from macro 'assert' npm ERR! (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __ASSERT_FILE_NAME, __LINE__, #e) : (void)0) npm ERR! ^ npm ERR! In file included from ../src/microtime.cc:9: npm ERR! In file included from ../../nan/nan.h:2722: npm ERR! ../../nan/nan_object_wrap.h:127:26: error: no member named 'IsNearDeath' in 'Nan::Persistent<v8::Object>' npm ERR! assert(wrap->handle_.IsNearDeath()); npm ERR! ~~~~~~~~~~~~~ ^ npm ERR! /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/assert.h:99:25: note: expanded from macro 'assert' npm ERR! (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __ASSERT_FILE_NAME, __LINE__, #e) : (void)0) npm ERR! ^ npm ERR! In file included from ../src/microtime.cc:9: npm ERR! In file included from ../../nan/nan.h:2818: npm ERR! ../../nan/nan_typedarray_contents.h:34:43: warning: 'GetContents' is deprecated: Use GetBackingStore. See http://crbug.com/v8/9908. [-Wdeprecated-declarations] npm ERR! data = static_cast<char*>(buffer->GetContents().Data()) + byte_offset; npm ERR! ^ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:5614:3: note: 'GetContents' has been explicitly marked deprecated here npm ERR! V8_DEPRECATED("Use GetBackingStore. See http://crbug.com/v8/9908.") npm ERR! ^ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8config.h:454:35: note: expanded from macro 'V8_DEPRECATED' npm ERR! # define V8_DEPRECATED(message) [[deprecated(message)]] npm ERR! ^ npm ERR! ../src/microtime.cc:75:10: error: no matching member function for call to 'Set' npm ERR! array->Set(Nan::New<v8::Integer>(0), Nan::New<v8::Number>((double)t.tv_sec)); npm ERR! ~~~~~~~^~~ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:3961:37: note: candidate function not viable: requires 3 arguments, but 2 were provided npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, npm ERR! ^ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:3964:37: note: candidate function not viable: requires 3 arguments, but 2 were provided npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, npm ERR! ^ npm ERR! ../src/microtime.cc:76:10: error: no matching member function for call to 'Set' npm ERR! array->Set(Nan::New<v8::Integer>(1), Nan::New<v8::Number>((double)t.tv_usec)); npm ERR! ~~~~~~~^~~ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:3961:37: note: candidate function not viable: requires 3 arguments, but 2 were provided npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, npm ERR! ^ npm ERR! /Users/yangjia/Library/Caches/node-gyp/16.14.0/include/node/v8.h:3964:37: note: candidate function not viable: requires 3 arguments, but 2 were provided npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, npm ERR! ^ npm ERR! 1 warning and 9 errors generated. npm ERR! make: *** [Release/obj.target/microtime/src/microtime.o] Error 1 npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2 npm ERR! gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:520:28) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) npm ERR! gyp ERR! System Darwin 22.6.0 npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" npm ERR! gyp ERR! cwd /Users/yangjia/workspace/company/dkYun/SDK2.0/node_modules/microtime npm ERR! gyp ERR! node -v v16.14.0 npm ERR! gyp ERR! node-gyp -v v8.4.1 npm ERR! gyp ERR! not ok npm ERR! A complete log of this run can be found in: npm ERR! /Users/yangjia/.npm/_logs/2025-06-30T06_40_09_765Z-debug-0.log
07-01
[^1]:引用自清除node-gyp缓存和重新安装构建工具步骤[^2]:引用自npm安装报错日志位置提示[^3]:引用自使用淘宝镜像安装microtime的方法[^4]:引用自node-gyp编译需要Node.js源代码的解释§§相关问题§§1....
执行npm cache clean --force报错npm error Class extends value undefined is not a constructor or null
05-01
然而，在某些情况下，可能会遇到类似于 `Class extends value undefined is not a constructor or null` 的错误。这种错误通常表明存在以下几种潜在原因： #### 可能的原因 1. **Node.js 或 npm 版本不兼容** ...
npm使用socks代理
jiumengyuan的博客
08-13 731
在node环境下使用http-proxy-to-socks工具将http代理转化为socks代理，来实现npm间接使用socks代理
Cannot find module ‘https-proxy-agent‘
子燕若水的博客
12-21 2772
成功解决：Cannot find module 'https-proxy-agent' 解决之后： 解决方案：
使用http-proxy-middleware报错显示proxy is not a funcion
认定的总要想办法去完成。
02-23 2110
前言  下载并使用http-proxy-middleware包时，显示报错，代码如下： const express = require('express'); const proxy = require('http-proxy-middleware') const app = express() app.use(express.static(__dirname + '/')) app.use('/api', proxy({ target: 'http://localhost:40
Http-proxy-middleware 报错：proxy is not a function
热爱思考、活力满满、开朗爱笑的年轻人
05-10 2006
Http-proxy-middleware 报错：proxy is not a function问题重现解决办法参考文档 问题重现 在使用 http-proxy-middleware 做接口代理的时候， //引入跨域中间件 let proxy = require('http-proxy-middleware'); //这里要注意"^/" 是匹配的路由,它会将匹配的路由进行转发，没匹配到的就不会转发。 app.use('/api', proxy({ //目标后端服务地址 target: 'htt
给socks-proxy-agent增加认证
YANTAI123456789的博客
06-03 757
由于需要使用socks代理，查看了nodejs的各种socks库，最终的结论是socks库是其中最完善的，而socks-proxy-agent是以其为基础的封装，可以直接和http模块对接。 不过在尝试后发现socks-proxy-agent建立的连接无法使用认证功能，而直接使用socks库是可以的。因此查看了其源码。 var options = { proxy: ...
Cannot find module ‘https-proxy-agent‘ 是因为没有root权限
yjm919的博客
08-13 629
wscat运行时，出现 Cannot find module 'https-proxy-agent' 是因为没有root权限。或者su转入root权限就可以了。
报错：is not a construction (npm/cdn第三方依赖包或插件)
haohaohaowa的博客
07-08 316
is not a construction
评论 1
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值