You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integrates ShellCheck into VS Code, a linter for Shell scripts.
Quick start
Disclaimer
This VS Code extension requires ShellCheck (the awesome static analysis tool for shell scripts) to work, but precompiled ShellCheck binaries are bundled in this extension for these platforms:
Linux (x86_64, arm64, arm)
macOS (x86_64, arm64)
Windows (x86_64, arm64 with the x86_64 binary)
Troubleshooting
If ShellCheck seems not working, a helper command ShellCheck: Collect Diagnostics For Current Document from the Command Palette is provided to help troubleshooting.
Options
There are various options that can be configured by making changes to your user or workspace preferences.
To add additional ignore patterns atop the default patterns, you have to copy the default ignore patterns and then add yours to the end of the list (#1196).
Fix all errors on save
The auto-fixable errors can be fixed automatically on save by using the following configuration:
Alternatively, you can fix all errors on demand by running the command Fix All in the VS Code Command Palette.
Lint onType or onSave
By default the linter will lint as you type. Alternatively, set shellcheck.run to onSave if you want to lint only when the file is saved (works best if auto-save is on).
{
"shellcheck.run": "onType"// also: "onSave"
}
Excluding Checks
By default all ShellCheck checks are performed and reported on as necessary. To globally ignore certain checks in all files, you can use a .shellcheckrc at the workspace root. For example, to exclude SC1017:
# .shellcheckrcdisable=SC1017
As last resort, you can also add the SC identifiers to shellcheck.exclude extension setting. For example, to exclude SC1017:
{
"shellcheck.exclude": ["1017"]
}
Using ShellCheck through Docker
In order to get it working, you need a shim script. Avoid including ShellCheck arguments in it.
Here is a simple shim script to get started with (see discussion: #24):
For example, you can place it at shellcheck.sh in the root of your workspace with execution permission (chmod +x shellcheck.sh).
You can can then configure the extension to use it with:
// .vscode/settings.json
{
// use the shim as shellcheck executable"shellcheck.executablePath": "${workspaceFolder}/shellcheck.sh",
// you may also need to turn this option on, so shellcheck in the container// can access all the files in the workspace and not only the directory// where the file being linted is."shellcheck.useWorkspaceRootAsCwd": true
}
Just have in mind that this should come with a performance hit, as booting up a docker container is slower than just invoking the binary.
Advanced usage
Integrating other VS Code extensions
This extension provides a small API, which allows other VS Code extensions to interact with the ShellCheck extension. For details, see API.md.