MuriloKakazu
commented
4 years ago Just to give an update on this, I eventually managed to make it work, so here's what I did:
I've upgraded to Ubuntu 20.04 (not because of this, but since I did, it would not hurt to try again), and trying to install the local server plugin now at least spit the following error:
error /root/.local/share/sfdx/node_modules/core-js-pure: Command failed.
Exit code: 139
Command: node -e "try{require('./postinstall')}catch(e){}"
Arguments:
Directory: /root/.local/share/sfdx/node_modules/core-js-pure
Output:
Segmentation fault (core dumped)Weird. So I uninstalled sfdx, nodejs, npm:
sudo npm remove sfdx-cli
sudo apt --auto-remove purge nodejs
sudo apt --auto-remove purge npmAlso removed remaining stuff just to be sure:
sudo rm -rf /usr/local/bin/npm /usr/local/share/man/man1/node* /usr/local/lib/dtrace/node.d ~/.npm ~/.node-gyp /opt/local/bin/node /opt/local/include/node /opt/local/lib/node_modules
sudo rm -rf /usr/local/lib/node*
sudo rm -rf /usr/local/include/node*
sudo rm -rf /usr/local/bin/node*
sudo rm -rf /usr/local/lib/sfdx*
sudo rm -rf /usr/local/bin/sfdx*reinstalled nodejs, npm and sfdx again:
sudo apt install npm
sudo npm install --global sfdx-cliThen... I could successfully install the plugin this time!
sfdx plugins:install @salesforce/lwc-dev-server && sfdx plugins
output:
@salesforce/lwc-dev-server 1.0.10
├─ @oclif/plugin-update 1.3.9
└─ @oclif/plugin-help 2.2.3
Describe the bug Can't set up the local dev env. @salesforce/lwc-dev-server plugin install fails silently
To Reproduce
Output is:
no plugins installedAnd if I run
sfdx force:lightning:lwc:startit echoes the following:Expected behavior I expect the plugin to be installed, or at least errors to be spit out so I can try to troubleshoot
Screenshots
Desktop (please complete the following information):
Additional context Running
DEBUG=* sfdx plugins:install @salesforce/lwc-dev-serveroutputs the following:I checked the troubleshooting docs for silent install failures and found something related to this subject, but that does not seem to be the my case since my user already has read, write and execute permissions in both npm directories. And it would not matter anyway since I tried installing the plugin as super user and it still failed silently.