forcedotcom / lwc-dev-server-feedback

LWC Local Development
BSD 3-Clause "New" or "Revised" License
45 stars 10 forks source link

Can't start a local development server. CLIError: timed out. LWR6004: Server is shutdown #141

Open mikhailivanov opened 1 year ago

mikhailivanov commented 1 year ago

Describe the bug

I am using the command sfdx force:lightning:lwc:start -u TMS/develop.

There is a log:

` Use of this plugin is subject to the Salesforce.com Program Agreement.
By installing this plugin, you agree to the Salesforce.com Program Agreementhttps://trailblazer.me/terms and acknowledge the Salesforce Privacy Policyhttps://www.salesforce.com/company/privacy.jsp.

Starting LWC Local Development.
Username: test-y9paklqolmqe@example.com Api Version: 49.0

Custom labels 'C:\Work\DX\TMS_DX\sfdx-source\TMS\main\default\labels\CustomLabels.labels-meta.xml' were not found [HPM] Proxy created: / -> https://innovation-power-8798-dev-ed.my.salesforce.com [HPM] Subscribed to http-proxy events: [ 'proxyReq', 'error', 'close' ] LWR6003: Listening on :3333 Server up on http://localhost:3333 LWR6000: Created version hash "57fe29aad4" CLIError: timed out at Object.error (C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\errors\index.js:28:15) at C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:25:66 at async flush (C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9) { oclif: { exit: 2 }, code: undefined } CLIError: timed out at Object.error (C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\errors\index.js:28:15) at C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:25:66 at async flush (C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9) { oclif: { exit: 2 }, code: undefined } LWR6004: Server is shutdown Error: timed out at Object.error (C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\errors\index.js:28:15) at C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:25:66 at async flush (C:\Users\User\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9) `

Expected behavior It should run the server without the unexpected shutdown.

Desktop (please complete the following information):

kaustubh-wakhare-isobar commented 1 year ago

Getting same issue

After running command sfdx force:lightning:lwc:start ` Starting LWC Local Development. Username: test-z1pqjbmf3duy@example.com Api Version: 49.0

[HPM] Proxy created: / -> https://connect-customization-3267-dev-ed.my.salesforce.com [HPM] Subscribed to http-proxy events: [ 'proxyReq', 'error', 'close' ] cp: no such file or directory: C:/Users/kaustubh.wakhare/OneDrive - dentsu/Documents/B2B/ToDo-Manager/force-app/main/default/staticresources/ cp: no such file or directory: C:/Users/kaustubh.wakhare/OneDrive - dentsu/Documents/B2B/ToDo-Manager/force-app/main/default/contentassets/ LWR6003: Listening on :3333 Server up on http://localhost:3333 LWR6000: Created version hash "d5fe1f17e8" CLIError: timed out at Object.error (C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\errors\index.js:28:15) at C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:25:66 at async flush (C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9) { oclif: { exit: 2 }, code: undefined } CLIError: timed out at Object.error (C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\errors\index.js:28:15) at C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:25:66 at async flush (C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9) { oclif: { exit: 2 }, code: undefined } LWR6004: Server is shutdown Error: timed out at Object.error (C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\errors\index.js:28:15) at C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:25:66 at async flush (C:\Users\kaustubh.wakhare\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9)` Expected behavior It should run the server without the unexpected shutdown.

OS: Windows 10

And updated latest sfdx version

lxw-2000 commented 1 year ago

CLIError: timed out at Object.error (C:\Users\Administrator\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\errors\index.js:28:15) at C:\Users\Administrator\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:25:66 at async flush (C:\Users\Administrator\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9) { code: undefined } --------------------------------------------my solution------------------------------------ into C:\Users\Administrator\AppData\Local\sfdx\client\7.163.0-ea5a9c6\node_modules\@oclif\core\lib\cli-ux\index.js:121:9 and
update async flush() { await timeout(flush(), 10000000); //set timeout 10000000,the old is 10000! },

stale[bot] commented 1 year ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.