ember.js “错误:如果已在使用ember服务器上运行生成,则无法启动生成”

af7jpaap  于 2022-11-05  发布在  其他
关注(0)|答案(1)|浏览(113)

我刚在Ember建立了一个项目,我遇到了这个问题。它不会消失。我检查了很多论坛。
我在运行ember server时遇到此错误

Cannot start a build if one is already running

Stack Trace and Error Report: /var/folders/gg/_8df84q97d9bv3hvcky3sj1c0000gn/T/error.dump.9aec39b1e1cb7d4551398e66431a9697.log

Build successful (5256ms) – Serving on http://localhost:4200/

Slowest Nodes (totalTime => 5% )              | Total (avg)         
----------------------------------------------+---------------------
BroccoliRollup (6)                            | 1152ms (192 ms)     
SassCompiler (1)                              | 1086ms              
Babel: @ember/test-helpers (2)                | 550ms (275 ms)      
Package /assets/vendor.js (1)                 | 391ms               
ember-auto-import-analyzer (3)                | 382ms (127 ms)      
broccoli-persistent-filter:EslintValid... (2) | 285ms (142 ms)      

(node:5414) UnhandledPromiseRejectionWarning: Error: Cannot start a build if one is already running
    at Builder.build (/Users/freakyspeedster/Documents/cash-n/cashn-wallet/node_modules/broccoli/dist/builder.js:100:19)
    at /Users/freakyspeedster/Documents/cash-n/cashn-wallet/node_modules/ember-cli/lib/models/builder.js:220:32
    at tryCatcher (/Users/freakyspeedster/Documents/cash-n/cashn-wallet/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:326:21)
    at invokeCallback (/Users/freakyspeedster/Documents/cash-n/cashn-wallet/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:498:33)
    at publish (/Users/freakyspeedster/Documents/cash-n/cashn-wallet/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:484:9)
    at flush (/Users/freakyspeedster/Documents/cash-n/cashn-wallet/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:2441:7)
    at processTicksAndRejections (internal/process/task_queues.js:75:11)
    at runNextTicks (internal/process/task_queues.js:62:3)
    at processTimers (internal/timers.js:472:9)
2lpgd968

2lpgd9681#

这看起来是一个issue in ember-cli。这个问题现在已经在broccoli@3.4.1的发布中得到了解决。获得最新broccoli版本的最简单的方法就是删除你的锁定文件并重新安装。

rm package-lock.json
npm install

相关问题