Hide selected folders in VS Code for a cleaner workspace.
- Hide/unhide folders per-workspace.
- Settings stored in
.vscode/settings.json(invisifolder.hiddenFolders). - Explorer context menu and Status Bar management.
- Updates
files.excludeto hide folders from Explorer.
Invisifolder: Hide Folder— Hide a folder (Explorer context menu or command palette).Invisifolder: Unhide Folder— Remove a folder from hidden list (command palette or status bar).- Click the status bar item to manage hidden folders with a quick menu.
Hidden folders are saved in workspace settings:
"invisifolder.hiddenFolders": ["dist", "build"]The extension will map these to files.exclude patterns.
If someone else is not using Invisifolder, the hidden folders will still be hidden in Explorer due to the
files.excludesettings.
-
Via Explorer Context Menu: Right-click any folder in the Explorer and select "Invisifolder: Hide Folder"
-
Via Command Palette: Press
Ctrl+Shift+P(orCmd+Shift+Pon Mac), type "Invisifolder: Hide Folder", and follow the prompts -
Via Status Bar: Click the Invisifolder status bar item (shows "👁️🗨️ Invisifolder: X") and select "Add folder"
-
Via Command Palette: Press
Ctrl+Shift+P, type "Invisifolder: Unhide Folder", and select a folder from the list -
Via Status Bar: Click the Invisifolder status bar item and select "Remove folder"
Managing Hidden Folders
Click the status bar item to see a quick overview of hidden folders and manage them through a convenient menu.
The extension stores hidden folders in your workspace settings (.vscode/settings.json):
{
"invisifolder.hiddenFolders": [
"dist",
"packages/foo/build"
],
"files.exclude": {
"dist/**": true,
"packages/foo/build/**": true
}
}- Clone the repository
- Run
npm installto install dependencies - Run
npm run compileto compile TypeScript - Press
F5to open a new Extension Development Host window
This extension uses automated GitHub Actions for publishing:
- Get a Personal Access Token (PAT) from Visual Studio Marketplace
- Add the PAT as a repository secret named
VSCE_PATin GitHub Settings → Secrets and variables → Actions
- Automatic: Create a new GitHub release with a version tag (e.g.,
v1.0.0)- Stable releases: Use normal releases
- Pre-releases: Check "This is a pre-release" option
- Manual: Use the "Publish VS Code Extension" workflow dispatch in GitHub Actions
The workflows will:
- Build and test the extension on multiple platforms
- Package the extension as a
.vsixfile - Publish to VS Code Marketplace
- Attach the
.vsixfile to the GitHub release
MIT





