There is no formatter for "shellscript" files installed
I have tested this on a new vscode (latest versions windows x64) and it's the same.
I cannot set a default formatter for shellscript or any default langauge using latest release.
If I roll back to previous version it works fine.
shfmt is latest version.
simple workaround
A practical workaround was added by @ehoogeveen-medweb here
Read comments after to see various methods of installation on your platform.
tl:dr
Download https://unpkg.com/@one-ini/[email protected]/one_ini_bg.wasm and put it in
VSCode/data/extensions/foxundermoon.shell-format-7.2.8/dist/one_ini_bg.wasm
Algorithm : SHA1
Hash : AC8750AC936A12F90DEAC5CBC5DDE7F977797AC7
Path : one_ini_bg.wasm
Algorithm : SHA256
Hash : C5AF9AFBC40CE6702E28E4BFE46A72EBF1EFC30F2E3BDF8F9B9E14CE9420A270
Path : one_ini_bg.wasm
same on mac os , at now solution is downgrade
same, resolved after downgrade
The same problem, I have to downgrade:
Tried to fix this: https://github.com/foxundermoon/vs-shell-format/pull/397
Solution Found: Downgrading to v7.2.5 resolves the issue. Hope this helps others facing the same issue.
Same problem -- reports like this for me.
Extension 'shell-format' is configured as formatter but it cannot format 'Shell Script'-files
Downgrading to v7.2.5 resolves
I can confirm the issue. I had to downgrade to v 7.2.5
I also encountered the same problem.
I am experiencing the same issue :c :C cry on LINUX UBUNTU 24.04 . i even made my own custon installation script to complement the super awsome foxundermoon.shell-format extension [ so that it can use the most recent shfmt binary version (from the stock default v3.6.0 to be fetching the most recent one dynamically and auto configure vscode settings to use it, current version is shfmt_v3.12.0_linux_amd64 by the way)]
If anyone wants it, its on my github repo. APT-AUTO-INSTALLS>WARES-LIB>LINUX-GNOME-AND-MATE-DE-LIB>FOR_LINUX_GNOME_AND_MATE_DE_LIB_EXT_LIB ... its in the vscode installation section
ERROR: Extension 'shell-format' is configured as formatter but it cannot format 'Shell Script'-files on LINUX UBUNTU 24.04 and debian 13 "trixie"
a downgrade to previous version seems to be a viable quick fix for now sad :c 🌵 .... careless whisper plays in the background, sad vibes today
I can also confirm the issue with the latest update on Linux (Pop!_OS 22.04) even though I specified the shfmt path in settings.json for all profiles correctly. I had to downgrade to v7.2.5.
Solution Found: Downgrading to v7.2.5 resolves the issue. Hope this helps others facing the same issue.
Any updates? Has the problem been fixed yet?
Solution Found: Downgrading to v7.2.5 resolves the issue. Hope this helps others facing the same issue.
Any updates? Has the problem been fixed yet?
No but it's not an emergency.
Previous version is fully functional and works fine until maintainer can resolve issues.
Solution Found: Downgrading to v7.2.5 resolves the issue. Hope this helps others facing the same issue.
Any updates? Has the problem been fixed yet?
No but it's not an emergency.
Previous version is fully functional and works fine until maintainer can resolve issues.
Logically, that makes sense, but intuitively, the author can simply revert version 7.2.8 since it's faulty. Reverting it would resolve many issues without much effort and prevent more people from commenting on this issue.
a downgrade to previous version seems to be a viable quick fix for now
VSCodium only offers one previous version, 7.0.1. Need to download shell-format-7.2.5.vsix from Releases and install it.
the author can simply revert version 7.2.8
v. 7.2.7 has the same issue. Need to revert to v.2.7.5.
Same problem, I thought it was a VSCode update that was broken
Same problem here; working in 2.7.5 though.
Same problem on Fedora Linux. The older version works fine.
same issue in windows 7.2.8 , 7.2.5 is fine .
Tried to fix this: #397
The author seems to abandon this project. Could you please make another project like "vs-shell-format-reborn"(or whatever name you like) and public to vscode marketplace? Thanks.
Tried to fix this: #397
The author seems to abandon this project. Could you please make another project like "vs-shell-format-reborn"(or whatever name you like) and public to vscode marketplace? Thanks.
It's too early to say. The maintainers just updated the version recently (though not sure why the fix was slow). I think they'll resolve it once they see it.
shell-format-pinned-7.2.5.vsix.remove-ext.dmp
use this vsix file to block the annoying extension update badge. I change some meta data to block auto update check.
Tried to fix this: #397
The author seems to abandon this project. Could you please make another project like "vs-shell-format-reborn"(or whatever name you like) and public to vscode marketplace? Thanks.
大L他疯了,要搞个新和连胜. XD
Tried to fix this: #397
The author seems to abandon this project. Could you please make another project like "vs-shell-format-reborn"(or whatever name you like) and public to vscode marketplace? Thanks.
大L他疯了,要搞个新和连胜. XD
主要是天天盯着那个更新提示,有点头疼了
Tried to fix this: #397
The author seems to abandon this project. Could you please make another project like "vs-shell-format-reborn"(or whatever name you like) and public to vscode marketplace? Thanks.
大L他疯了,要搞个新和连胜. XD
主要是天天盯着那个更新提示,有点头疼了
我也一样, 看着很烦.
I encountered the same issue in the following versions, but reverting vs-shell-format to 7.2.5 resolved the problem.
Visual Studio Code Version: 1.102.1 Commit: 7adae6a56e34cb64d08899664b814cf620465925 Date: 2025-07-15T16:41:17.147Z (6 days ago) Electron: 35.6.0 ElectronBuildId: 11847422 Chromium: 134.0.6998.205 Node.js: 22.15.1 V8: 13.4.114.21-electron.0 OS: Darwin arm64 24.3.0
vs-shell-format Version: 7.2.8
On MacOS VSCode 1.102.2.
~~Downgrading to 7.2.5 doesn't solve the issue for me. Tried another extension shfmt and it has the same issue.~~
7.2.5 works after I re-pick it as shell script formatter.
Another complete hack is to clone this repo, yarn install, then cp ./node_modules/@one-ini/wasm/one_ini_bg.wasm $HOME/.vscode/extensions/foxundermoon.shell-format-7.2.8/dist/. I'm still trying to figure out where it's being required. But this'll get you back to 7.2.8 until the owner can fix.
if it's not working for everyone, why version 7.2.5 is not being pushed with a new version number, while this is being fixed?