antfu/vscode-file-nesting-config

Config of File Nesting for VS Code

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Type:Configuration / DotfilesCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on September 19th, 2026
Created on March 8th, 2022
Open Issues & Pull Requests: 23 (+0)
GitHub issues: Enabled
Number of forks: 202
Total Stargazers: 3,665 (+0)
Total Subscribers: 13 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 162.1 days
90th percentile: 574.2 days
Tracked items: 24

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 446 days
Stale 30+ days: 11
Stale 90+ days: 10

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (22)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

vscode-file-nesting-config is a configuration preset for VS Code that organizes your file explorer using the editor's file nesting feature.

The tool solves the problem of cluttered file trees by automatically nesting related files under parent files. VS Code's file nesting feature allows you to define rules that hide certain files beneath others in the explorer view, reducing visual noise. This configuration provides a ready-made set of nesting rules designed to work across common project types and file patterns, eliminating the need to manually craft these rules yourself.

Developers should adopt this if they want an immediate, opinionated file organization scheme without configuring nesting rules from scratch. The tool works best for projects using standard file naming conventions where related files naturally group together. The project offers two paths to adoption: you can manually copy the configuration snippet into your VS Code settings, or use the accompanying VS Code extension to have updates applied automatically. The configuration is generated by script to avoid duplication, and contributors are directed to modify the generation script rather than edit configuration directly.

The project maintains an active development approach with automated tooling at its core. The codebase includes scripts that generate the configuration output, ensuring consistency and reducing manual maintenance burden. The project accepts contributions through pull requests with clear guidance on the proper workflow for making changes.