Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to install LWC plugin lwc-dev-server #120

Open
DeveloperSudipto opened this issue Jul 10, 2021 · 7 comments
Open

Not able to install LWC plugin lwc-dev-server #120

DeveloperSudipto opened this issue Jul 10, 2021 · 7 comments

Comments

@DeveloperSudipto
Copy link

Hi ,

I am getting below error while installing the plugin for lwc-dev-server.Please help.

error C:\Users\USER\AppData\Local\sfdx\node_modules\fibers: Command failed.
Exit code: 1
Command: node build.js || nodejs build.js
Arguments:
Directory: C:\Users\USER\AppData\Local\sfdx\node_modules\fibers
Output:
Build succeeded but target not found
'nodejs' is not recognized as an internal or external command,
operable program or batch file.
Installing plugin @salesforce/lwc-dev-server... failed
Error: yarn add @salesforce/lwc-dev-server@latest --non-interactive
--mutex=file:C:\Users\USER\AppData\Local\sfdx\yarn.lock
--preferred-cache-folder=C:\Users\USER\AppData\Local\sfdx\yarn --check-files exited with code 1

@ronkiker
Copy link

since you're using windows, did you need set the node.js folder path into your system variables or user variables?

@DeveloperSudipto
Copy link
Author

Yes @ronkiker . Path is set as C:\Program Files\nodejs\

@stale
Copy link

stale bot commented Jul 19, 2021

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

@stale stale bot added the type:bug-p3 label Jul 19, 2021
@kashyapkbandi
Copy link

  • 1 .
    I have tried uninstalling & reinstalling node.
    with + without vpn.
    Can see the same issue.

@stale stale bot removed the type:bug-p3 label Jul 20, 2021
@stale
Copy link

stale bot commented Jul 27, 2021

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

@stale stale bot added the type:bug-p3 label Jul 27, 2021
@rrgpal-dev
Copy link

this problem has no right solution, this is still not resolved

@stale stale bot removed the type:bug-p3 label Jun 19, 2022
@stale
Copy link

stale bot commented Jun 28, 2022

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

@stale stale bot added the type:bug-p3 label Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants