-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
VSC hint popped up saying: extension 'Standard- Javascript standard style' is configured as formatter but it cannot format javascript files. #331
Comments
VSC settings.json contents are: { |
Hi, I have the same issue |
same here
|
also receiving this error in VS Code. Have tried remove all other formatters and resetting VS Code settings to defaults. Have tried uninstall and re-install in the latest plugin, as well as updating to latest "standard": "^16.0.4", options in package.json "standard": {
"globals": [
"$",
"jQuery",
"can",
"mocha"
],
"ignore": [
"src/calculator/",
"models/fixtures/**",
"mobile/util/**",
"build.production.html.js",
"styles/documentjs-theme/**",
"models/tests/fixtures/**"
],
"env": [
"mocha"
]
}, If I run |
I'm hitting this same issue as well. it's a bit frustrating to that this extension deviates from the vscode convention in this way |
I have the same problem. "Fix all auto-fixable-problems" works but using standardjs as formatter throws this error on the same file. |
I know that going with "same here" does not really help, but this issue is 2 years old and I don't see any further feedback from members besides the initial "can't reproduce". I'd like to understand if this is an issue afflicting only a few of us and won't be addressed or if it is something widespread. Given that the main function of the formatter itself is hindered by this issue it does not make much sense to use the extension at all if the issue persists. |
happens to me too |
same here |
1 similar comment
same here |
following settings fixed the issue for me "standard.enable": true,
"standard.enableGlobally": true,
"standard.run": "onType", // in my case "onType" fixes on save, "onSave" seems to fix only on auto save, doesn't do anything on ctrl+s
"standard.autoFixOnSave": true, // needs to be true with false both "onType" and "onSave" doesn't work
"standard.treatErrorsAsWarnings": true,
"standard.engine": "standard",
"standard.validate": [
"javascript",
"javascriptreact",
"typescript",
"typescriptreact"
],
"[javascript]": {
"editor.formatOnSave": true,
"editor.defaultFormatter": "standard.vscode-standard"
}, |
What version of this package are you using? v2.0.1
What operating system, Node.js, and npm version? macos Monterey 12.0.1 with Node v17.1.0 and [email protected], [email protected] is installed globaly.
What happened? Popup showed when trigger formatter via hotkey combo option+shift+f
What did you expect to happen? No popup should be showed and code should be formatted by standard.
Are you willing to submit a pull request to fix this bug? If I could, I would ^_^.
The text was updated successfully, but these errors were encountered: