npm编译error：134

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

#npm #javascript #前端

当React项目打包遇到错误134，通常是由于项目过大导致内存不足。解决方案包括在package.json中设置max_old_space_size参数，增加内存分配，或者通过命令行设置NODE_OPTIONS环境变量。如果这些方法无效，可以尝试删除node_modules及清理npm缓存，甚至升级Node.js版本来解决问题。

项目场景：

react项目npm run build打包

问题描述

出现错误提示error: 134在这里插入图片描述

原因分析：

react项目太大，分配的内存不够多，内存溢出

解决方案：

1：在package.json中修改start和build

"start": "react-scripts --max_old_space_size=46384 start",
"build": "react-scripts --max_old_space_size=46384 build",

然后npm run build编译，如果还是报错134。

2：扩充内存：在cmd中运行 set NODE_OPTIONS=–max_old_space_size=8096
然后npm run build编译，如果还是报错134。

3、将node-modules文件夹先删除，删除C:\Users\用户名\AppData\Roaming中的npm和npm-cache文件夹（AppData是隐藏文件夹），npm install下载依赖，然后npm run build编译

4、升级nodejs

阿丙_zl
关注
vue项目 ‘npm run dev‘ 报错 npm ERR! errno 134
jieyucx的博客
06-27 5721
这时需要我们分配更多的内存给。
npm run xxxx报错134
v_vszhao的博客
04-14 295
npm运行报错134
vue启动报错 npm ERR! Exit status 134
lzw_yinghua的博客
10-10 141
vue启动报错
运行vue项目时报npm ERR! Exit status 134
qq_34424698的博客
04-18 545
运行vue项目时报npm ERR! Exit status 134
【Vue问题解决记录】npm ERR! errno 134
weixin_44991457的博客
02-18 1867
提示：文章写完后，目录可以自动生成，如何生成可参考右边的帮助文档。
Vue 项目报错 npm err code elifecycle npm err errno 134
JustForCOPY的博客
02-13 1827
Vue项目启动内存溢出报错
npm start 内存溢出错误 Error 134
qq_41515773的博客
10-15 2677
解决办法 执行： setx NODE_OPTIONS --max_old_space_size=4096
记录一下，解决js内存溢出npm ERR! code ELIFECYCLEnpm ERR! errno 134 以及 errno 9009
weixin_57237676的博客
12-05 2746
解决npm ERR! code ELIFECYCLEnpm ERR! errno 134 和 npm ERR! code ELIFECYCLEnpm ERR! errno 9009
vue 项目打包报错error:134
weixin_48969871的博客
10-28 6053
百度了很多，发现是内存溢出的问题 解决办法： 在package.json中的build修改添加如下代码： npx --max-old-space-size=2048 打包成功啦！！
Vue 项目 npm run dev报错errno 134
weixin_45685108的博客
05-25 7784
报错信息： npm ERR! code ELIFECYCLE npm ERR! errno 134 npm ERR! GAWeb@1.0.0 nativeBuild: react-app-rewired build npm ERR! Exit status 134 npm ERR! npm ERR! Failed at the GAWeb@1.0.0 nativeBuild script. npm ERR! This is probably not a problem with npm. There is
记录一次npm run dev自动更新时报错134的问题
Afunwsnbb的博客
04-11 5133
npm报错js内存栈不足，npm自动更新失败！报错134 在公司电脑上一次又一次的出现了这个问题，代码一样，svn重新checkout下来的代码还是不行，加old/new空间也不好使。卸载webpack，安装旧版本也不好用。 难受了好几天，最终已经可以确认是webpack包的问题。 临时解决办法： 将同事代码中node-moudles/bin下面的最底部的关于webpack的六个文件替换掉...
npm run build 出现 Error: error:0308010C:digital envelope routines::unsupported
SecularBird的专栏
10-10 671
error:0308010C:digital envelope routines::unsupported 问题fix
C:\Users\admin\Desktop\nature>rmdir /s /q node_modules C:\Users\admin\Desktop\nature>del package-lock.json C:\Users\admin\Desktop\nature>npm install serialport@10.4.0 --verbose npm verb cli C:\nvm4w\nodejs\node.exe C:\nvm4w\nodejs\node_modules\npm\bin\npm-cli.js npm info using npm@8.19.3 npm info using node@v16.19.1 npm timing npm:load:whichnode Completed in 1ms npm timing config:load:defaults Completed in 1ms npm timing config:load:file:C:\Users\admin\AppData\Local\nvm\v16.19.1\node_modules\npm\npmrc Completed in 1ms npm timing config:load:builtin Completed in 1ms npm timing config:load:cli Completed in 1ms npm timing config:load:env Completed in 1ms npm timing config:load:file:C:\Users\admin\Desktop\nature\.npmrc Completed in 0ms npm timing config:load:project Completed in 10ms npm timing config:load:file:C:\Users\admin\.npmrc Completed in 1ms npm timing config:load:user Completed in 1ms npm timing config:load:file:C:\nvm4w\nodejs\etc\npmrc Completed in 0ms npm timing config:load:global Completed in 0ms npm timing config:load:validate Completed in 1ms npm timing config:load:credentials Completed in 1ms npm timing config:load:setEnvs Completed in 1ms npm timing config:load Completed in 18ms npm timing npm:load:configload Completed in 18ms npm timing npm:load:mkdirpcache Completed in 0ms npm timing npm:load:mkdirplogs Completed in 1ms npm verb title npm install serialport@10.4.0 npm verb argv "install" "serialport@10.4.0" "--loglevel" "verbose" npm timing npm:load:setTitle Completed in 1ms npm timing config:load:flatten Completed in 2ms npm timing npm:load:display Completed in 8ms npm verb logfile logs-max:10 dir:C:\Users\admin\AppData\Local\npm-cache\_logs npm verb logfile C:\Users\admin\AppData\Local\npm-cache\_logs\2025-11-28T09_22_54_627Z-debug-0.log npm timing npm:load:logFile Completed in 14ms npm timing npm:load:timers Completed in 0ms npm timing npm:load:configScope Completed in 0ms npm timing npm:load Completed in 44ms npm timing arborist:ctor Completed in 0ms npm timing arborist:ctor Completed in 0ms npm timing idealTree:init Completed in 10ms npm timing idealTree:userRequests Completed in 2ms npm http fetch GET 200 https://registry.npmmirror.com/serialport 184ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/ws 61ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/bufferutil 42ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/utf-8-validate 44ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/debug 139ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-inter-byte-timeout 154ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-spacepacket 162ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-packet-length 164ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-delimiter 166ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fbinding-mock 180ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fstream 182ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-ready 185ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-cctalk 192ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-regex 193ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-readline 212ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fbindings-cpp 223ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-byte-length 233ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fparser-slip-encoder 272ms (cache miss) npm timing idealTree:#root Completed in 624ms npm http fetch GET 200 https://registry.npmmirror.com/ms 72ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/node-addon-api 77ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/node-gyp-build 84ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fbindings-interface 154ms (cache miss) npm http fetch GET 200 https://registry.npmmirror.com/@serialport%2fbindings-interface 155ms (cache miss) npm timing idealTree:node_modules/serialport Completed in 176ms npm timing idealTree:node_modules/@serialport/binding-mock Completed in 2ms npm timing idealTree:node_modules/@serialport/bindings-cpp Completed in 4ms npm timing idealTree:node_modules/@serialport/bindings-interface Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-byte-length Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-cctalk Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-delimiter Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-inter-byte-timeout Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-packet-length Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-readline Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-ready Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-regex Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-slip-encoder Completed in 0ms npm timing idealTree:node_modules/@serialport/parser-spacepacket Completed in 0ms npm timing idealTree:node_modules/@serialport/stream Completed in 1ms npm timing idealTree:node_modules/debug Completed in 1ms npm timing idealTree:node_modules/ms Completed in 0ms npm timing idealTree:node_modules/node-addon-api Completed in 0ms npm timing idealTree:node_modules/node-gyp-build Completed in 0ms npm timing idealTree:node_modules/ws Completed in 0ms npm timing idealTree:node_modules/@serialport/bindings-cpp/node_modules/@serialport/bindings-interface Completed in 0ms npm timing idealTree:node_modules/@serialport/stream/node_modules/@serialport/bindings-interface Completed in 0ms npm timing idealTree:buildDeps Completed in 813ms npm timing idealTree:fixDepFlags Completed in 1ms npm timing idealTree Completed in 829ms npm timing reify:loadTrees Completed in 830ms npm timing reify:diffTrees Completed in 2ms npm timing reify:retireShallow Completed in 1ms npm timing reify:createSparse Completed in 11ms npm timing reify:loadBundles Completed in 0ms npm http fetch POST 404 https://registry.npmmirror.com/-/npm/v1/security/advisories/bulk 28ms npm http fetch POST 404 https://registry.npmmirror.com/-/npm/v1/security/audits/quick 16ms npm verb audit error HttpErrorGeneral: 404 Not Found - POST https://registry.npmmirror.com/-/npm/v1/security/audits/quick - [NOT_IMPLEMENTED] /-/npm/v1/security/* not implemented yet npm verb audit error at C:\Users\admin\AppData\Local\nvm\v16.19.1\node_modules\npm\node_modules\npm-registry-fetch\lib\check-response.js:95:15 npm verb audit error at processTicksAndRejections (node:internal/process/task_queues:96:5) npm verb audit error at async Map.[getReport] (C:\Users\admin\AppData\Local\nvm\v16.19.1\node_modules\npm\node_modules\@npmcli\arborist\lib\audit-report.js:335:21) npm verb audit error at async Map.run (C:\Users\admin\AppData\Local\nvm\v16.19.1\node_modules\npm\node_modules\@npmcli\arborist\lib\audit-report.js:106:19) npm verb audit error HttpErrorGeneral: 404 Not Found - POST https://registry.npmmirror.com/-/npm/v1/security/audits/quick - [NOT_IMPLEMENTED] /-/npm/v1/security/* not implemented yet npm verb audit error at C:\Users\admin\AppData\Local\nvm\v16.19.1\node_modules\npm\node_modules\npm-registry-fetch\lib\check-response.js:95:15 npm verb audit error at processTicksAndRejections (node:internal/process/task_queues:96:5) npm verb audit error at async Map.[getReport] (C:\Users\admin\AppData\Local\nvm\v16.19.1\node_modules\npm\node_modules\@npmcli\arborist\lib\audit-report.js:335:21) npm verb audit error at async Map.run (C:\Users\admin\AppData\Local\nvm\v16.19.1\node_modules\npm\node_modules\@npmcli\arborist\lib\audit-report.js:106:19) { npm verb audit error headers: [Object: null prototype] { npm verb audit error server: [ 'Tengine' ], npm verb audit error date: [ 'Fri, 28 Nov 2025 09:22:54 GMT' ], npm verb audit error 'content-type': [ 'application/json' ], npm verb audit error 'transfer-encoding': [ 'chunked' ], npm verb audit error connection: [ 'keep-alive' ], npm verb audit error 'strict-transport-security': [ 'max-age=5184000' ], npm verb audit error via: [ 'kunlun7.cn5212[,404666]' ], npm verb audit error 'timing-allow-origin': [ '*' ], npm verb audit error eagleid: [ '7ae4df1b17643217741033733e' ], npm verb audit error 'x-fetch-attempts': [ '1' ] npm verb audit error }, npm verb audit error statusCode: 404, npm verb audit error code: 'E404', npm verb audit error method: 'POST', npm verb audit error uri: 'https://registry.npmmirror.com/-/npm/v1/security/audits/quick', npm verb audit error body: { npm verb audit error error: '[NOT_IMPLEMENTED] /-/npm/v1/security/* not implemented yet' npm verb audit error }, npm verb audit error pkgid: undefined npm verb audit error } npm timing auditReport:getReport Completed in 59ms npm timing reify:audit Completed in 59ms npm timing reifyNode:node_modules/ms Completed in 105ms npm timing reifyNode:node_modules/@serialport/parser-regex Completed in 108ms npm timing reifyNode:node_modules/@serialport/parser-readline Completed in 108ms npm timing reifyNode:node_modules/@serialport/parser-packet-length Completed in 109ms npm timing reifyNode:node_modules/@serialport/parser-inter-byte-timeout Completed in 109ms npm timing reifyNode:node_modules/@serialport/parser-delimiter Completed in 110ms npm timing reifyNode:node_modules/@serialport/parser-cctalk Completed in 111ms npm timing reifyNode:node_modules/@serialport/parser-ready Completed in 111ms npm timing reifyNode:node_modules/@serialport/parser-byte-length Completed in 112ms npm timing reifyNode:node_modules/@serialport/stream Completed in 114ms npm timing reifyNode:node_modules/@serialport/bindings-interface Completed in 116ms npm timing reifyNode:node_modules/@serialport/parser-spacepacket Completed in 116ms npm timing reifyNode:node_modules/debug Completed in 117ms npm timing reifyNode:node_modules/@serialport/bindings-cpp/node_modules/@serialport/bindings-interface Completed in 117ms npm timing reifyNode:node_modules/@serialport/binding-mock Completed in 117ms npm timing reifyNode:node_modules/@serialport/stream/node_modules/@serialport/bindings-interface Completed in 119ms npm timing reifyNode:node_modules/node-gyp-build Completed in 120ms npm timing reifyNode:node_modules/@serialport/parser-slip-encoder Completed in 120ms npm timing reifyNode:node_modules/serialport Completed in 121ms npm timing reifyNode:node_modules/ws Completed in 131ms npm timing reifyNode:node_modules/node-addon-api Completed in 134ms npm timing reifyNode:node_modules/@serialport/bindings-cpp Completed in 197ms npm timing reify:unpack Completed in 198ms npm timing reify:unretire Completed in 1ms npm timing build:queue Completed in 10ms npm timing build:link:node_modules/node-gyp-build Completed in 24ms npm timing build:link Completed in 26ms npm info run @serialport/bindings-cpp@10.7.0 install node_modules/@serialport/bindings-cpp node-gyp-build npm info run @serialport/bindings-cpp@10.7.0 install { code: 0, signal: null } npm timing build:run:install:node_modules/@serialport/bindings-cpp Completed in 258ms npm timing build:run:install Completed in 258ms npm timing build:deps Completed in 295ms npm timing build Completed in 295ms npm timing reify:build Completed in 295ms npm timing reify:trash Completed in 0ms npm timing reify:save Completed in 6ms npm timing reify Completed in 1360ms added 22 packages in 2s 12 packages are looking for funding run `npm fund` for details npm timing command:install Completed in 1364ms npm verb exit 0 npm timing npm Completed in 1535ms npm info ok C:\Users\admin\Desktop\nature>dir node_modules\@serialport\bindings-cpp\build\Release\bindings.node 系统找不到指定的路径。 C:\Users\admin\Desktop\nature>
最新发布
11-29
| 找不到 Python | npm 找不到 python.exe | `npm config set python C:\Python39\python.exe` | | 下载超时 | 国内访问 GitHub 头文件慢 | 使用国内镜像： `npm config set disturl ...
npm报错Error: Node Sass version 7.0.1 is incompatible with ^4.0.0.
邓邓子的博客
03-17 2543
目录一、问题描述二、解决方法1.方法12.方法2 一、问题描述 npm 编译报错：Error: Node Sass version 7.0.1 is incompatible with ^4.0.0. Syntax Error: Error: Node Sass version 7.0.1 is incompatible with ^4.0.0. @ ./node_modules/vue-style-loader??ref--8-oneOf-1-0!./node_modules/css-loader
npm报错EPERM: operation not permitted
邓邓子的博客
07-16 7909
一、npm ERR! Error: EPERM: operation not permitted 以管理员身份运行即可 删除C:\Users\dengzy.npmrc也可以解决问题，但缓存文件和全局文件会生成在c盘，而不是自己设置的d盘： prefix=D:\Program Files\nodejs\node_global cache=D:\Program Files\nodejs\node_cache ...
vue启动编译时报错：134（内存溢出）
qq_40652539的博客
07-12 3191
vue项目启动报错，内存溢出，errno 134
npm ERR! code ELIFECYCLEnpm ERR! errno 134
xnian_的博客
08-19 5985
npm ERR! code ELIFECYCLEnpm ERR! errno 134
wow崩溃ERROR #134(0x85100086) Fatal Condition
skywalk8163的专栏
06-13 2012
判断是patch-zhCN-4.MPQ文件里的BakedNpc有问题，想进去MPQ里面改，但是没有趁手的软件。干脆把这个文件加上bak后缀注释掉了，结果问题解决了！wow 在一些特殊的地方容易崩溃，比如奥格飞行点往西， 幽暗的银月城传送宝珠那里。总结，就是相当于把这个文件删除。目前没有看到有什么影响。
npm err exit status 134
热门推荐
sjie123的博客
09-17 1万+
npm update npm rebuild delete node_modules and package-lock.json npm i
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值