Salesforcedx-vscode: nodePath assigned in workspace settings

Created on 30 Jan 2019  路  4Comments  路  Source: forcedotcom/salesforcedx-vscode

When I installed salesforce.salesforcedx-vscode-lwc it added the following setting to my workspace settings "eslint.nodePath": "/Users/john/.vscode/extensions/salesforce.salesforcedx-vscode-lwc-44.17.0/node_modules" .

Eslint broke for my project and all the subfolders. I spent much of the last couple days troubleshooting the issue.

lwc bug feedback

All 4 comments

@celador What do you mean by eslint broke? Just so I'm clear. My assumption is that you had your own ES Lint setup with custom settings and we forced vscode to use the one that ships with LWC which didnt work with your setup, is that correct?

We are not using eslint in our project but this is also causing us friction. Our project's .code-workspace files are committed to git so they can be shared across our team but now the vscode plugin is adding this "eslint.nodePath" setting which has a machine-dependent path which just mucks up the whole git commit process. This is an issue since we expect the .code-workspace files to remain machine agnostic.

UPDATE

In the interim, I'm using this trick to reduce the friction caused to our developer experience.

git update-index --skip-worktree *.code-workspace

This issue has been automatically closed because there has been no response to our request for more information from the original author. Currently, there is not enough information provided for us to take action. Please reply and reopen this issue if you need additional assistance.

Duplicate of #1248

Was this page helpful?
0 / 5 - 0 ratings