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

can't get the extension to work with WSL / global install #534

Open
ahmadnassri opened this issue Jul 22, 2023 · 1 comment
Open

can't get the extension to work with WSL / global install #534

ahmadnassri opened this issue Jul 22, 2023 · 1 comment

Comments

@ahmadnassri
Copy link

What version of this package are you using?

What operating system, Node.js, and npm version?

  • WSL / Ubuntu
  • node v20.5.0 (nvm)
  • npm v9.8.0

What happened?

when using the following configuration:

    "standard.enable": true,
    "standard.enableGlobally": true,
    "standard.usePackageJson": false,
    "standard.autoFixOnSave": true,
    "standard.validate": ["javascript", "javascript react"],
    "standard.nodePath": "/home/ahmad/.nvm/versions/node/v20.5.0/lib/node_modules",

I get the following error:

[Error - 10:35:53 AM] Failed to apply command: standard.applyAutoFix

if I remove the nodePath config, I get the following error instead:

[Info  - 10:36:24 AM] 
Failed to load the JavaScript Standard Style library for the document [...]/server.js

To use JavaScript Standard Style please install JavaScript Standard Style by running 'npm install standard' in the workspace folder node-serve-reload-replace
or globally using 'npm install -g standard'. You need to reopen the workspace after installing JavaScript Standard Style.

Alternatively you can disable JavaScript Standard Style for the workspace folder node-serve-reload-replace by executing the 'Disable JavaScript Standard Style' command.

What did you expect to happen?

should work without requiring to install standard as a direct project dependency.

Are you willing to submit a pull request to fix this bug?

If I have a clear direction to where the fix might be, sure.

@ahmadnassri
Copy link
Author

found my own issue again ... this has been plaguing me this whole time... still no resolution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant