forcedotcom / lwc-dev-server-feedback

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

sfdx force:lightning:lwc:start too many files #129

Open MGarfOppLoans opened 2 years ago

MGarfOppLoans commented 2 years ago

Summary

Running sfdx force:lightning:lwc:start causing too many files and error and crashs. Please switch it to use graceful-fs

Steps To Reproduce:

run sfdx force:lightning:lwc:start with a really large local repo of objects, classes, and more.

Expected result

Runs normally

Actual result

image

System Information

Run sfdx version --verbose --json and paste the output here.

{ "cliVersion": "sfdx-cli/7.120.0", "architecture": "wsl-x64", "nodeVersion": "node-v14.18.0", "pluginVersions": [ "@oclif/plugin-autocomplete 0.3.0 (core)", "@oclif/plugin-commands 1.3.0 (core)", "@oclif/plugin-help 3.2.3 (core)", "@oclif/plugin-not-found 1.2.4 (core)", "@oclif/plugin-plugins 1.10.1 (core)", "@oclif/plugin-update 1.5.0 (core)", "@oclif/plugin-warn-if-update-available 1.7.0 (core)", "@oclif/plugin-which 1.0.3 (core)", "@salesforce/lwc-dev-server 2.11.0", "@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)", "alias 1.1.10 (core)", "apex 0.2.9 (core)", "auth 1.7.1 (core)", "config 1.2.35 (core)", "custom-metadata 1.0.12 (core)", "data 0.6.1 (core)", "generator 1.2.0 (core)", "limits 1.2.1 (core)", "org 1.8.0 (core)", "salesforce-alm 52.3.5 (core)", "schema 1.0.8 (core)", "sfdx-cli 7.120.0 (core)", "source 1.2.0 (core)", "telemetry 1.2.4 (core)", "templates 52.2.0 (core)", "trust 1.0.8 (core)", "user 1.5.0 (core)" ], "osVersion": "Linux 5.10.16.3-microsoft-standard-WSL2" }

Additional information

Feel free to attach a screenshot.

github-actions[bot] commented 2 years ago

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

stale[bot] commented 2 years ago

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