search

forcedotcom / lwc-dev-server-feedback

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

Error While trying to install the PLugin for Local development Server #142

Open puvvadaverendra9 opened 1 year ago

puvvadaverendra9 commented 1 year ago

PS C:\Users\VEERENDRA PUVVADA> sfdx plugins:install @salesforce/lwc-dev-serversfdx plugins:install @salesforce/lwc-dev-server error An unexpected error occurred: "https://registry.yarnpkg.com/@salesforce%2flwc-dev-serversfdx: Not found". Installing plugin @salesforce/lwc-dev-serversfdx... failed Error: yarn add @salesforce/lwc-dev-serversfdx@latest --non-interactive --mutex=file:C:\Users\VEERENDRA PUVVADA\AppData\Local\sfdx\yarn.lock --preferred-cache-folder=C:\Users\VEERENDRA PUVVADA\AppData\Local\sfdx\yarn --check-files exited with code 1

gbockus-sf commented 1 year ago

I'm also seeing an error when attempting to install the plugin on macos although a different error.
We've been limited on time we could spend on this plugin for the past year or so. I'll call out to the PM that it is likely currently in a broken state and see if we can get some cycles to get it back up and running @AnanyaJha

stale[bot] commented 1 year ago

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

sairaman2112 commented 1 year ago

PS C:\Users\VEERENDRA PUVVADA> sfdx plugins:install @salesforce/lwc-dev-serversfdx plugins:install @salesforce/lwc-dev-server error An unexpected error occurred: "https://registry.yarnpkg.com/@salesforce%2flwc-dev-serversfdx: Not found". Installing plugin @salesforce/lwc-dev-serversfdx... failed Error: yarn add @salesforce/lwc-dev-serversfdx@latest --non-interactive --mutex=file:C:\Users\VEERENDRA PUVVADA\AppData\Local\sfdx\yarn.lock --preferred-cache-folder=C:\Users\VEERENDRA PUVVADA\AppData\Local\sfdx\yarn --check-files exited with code 1

I am also facing the errors while installing local server for lwc . please guide me if your problem got resolved.

stale[bot] commented 1 year ago

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