Config of File Nesting for VS Code
3.7k
Stars
204
Forks
22
Open issues
30
Contributors
AI Analysis
A curated VS Code configuration snippet that implements file nesting patterns to organize and declutter project file trees. It provides predefined nesting rules for common configuration files, build artifacts, and framework-specific files across JavaScript/TypeScript ecosystems. This tool is specifically for VS Code users who want a cleaner file explorer UI without changing their actual file structure.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Curated VS Code file nesting patterns for cleaner project explorers
vscode-file-nesting-config provides a JSON snippet of curated file grouping patterns for VS Code's native file nesting feature (v1.67+). It automatically hides configuration files, build artifacts, and type definitions under parent files in the explorer tree. Built by Anthony Fu for developers who want a cleaner workspace view. Adoption appears concentrated among JavaScript/TypeScript developers and framework users. The project also includes a VS Code extension for automatic updates.
Created March 2022 following viral tweets about VS Code's new file nesting feature. The author packaged hand-curated patterns for dozens of frameworks and tool ecosystems. Growth accelerated as more developers discovered the feature, with ongoing maintenance to add patterns for emerging tools (e.g., AI coding agents detected in June 2026 config update).
Moderate, steady adoption pattern. Project gained 3,651 stars over ~4 years (average ~900/year), with recent activity showing continued updates. The 5 stars in the last 7 days suggests organic but not explosive growth. A dedicated VS Code extension multiplier was added to automate config distribution. Growth appears driven by word-of-mouth discovery among developers who stumble upon the file nesting feature.
Adoption not verified through concrete metrics (GitHub stars alone do not confirm usage). However, circumstantial evidence suggests adoption: (1) 3,651 stars indicates significant discovery, (2) 205 forks show community interest in customization, (3) existence of dedicated VS Code extension suggests enough demand to justify separate tooling, (4) continued updates indicate the author believes it is being used. Real-world usage volume cannot be quantified from available data.
Based on README, the project is primarily a static JSON configuration template distributed via GitHub and a VS Code extension. The core is not application code but opinionated pattern definitions maintained via scripts to avoid duplication. The extension appears to handle auto-update logic, but README does not detail the extension's implementation.
Not documented in README. This is a configuration distribution project rather than executable code, so traditional test coverage is not applicable. Quality assurance appears to rely on community feedback and manual review of pattern accuracy.
Active. Last push on 2026-06-24 (10 days before analysis date) shows recent maintenance. README shows config last updated 2026-06-24 04:19, indicating ongoing curation. Repository has 205 forks and shows continued engagement, suggesting it is not dormant.
ADOPT IF: you use VS Code v1.67+, want a cleaner explorer view without manual configuration, and work in JavaScript/TypeScript or popular frameworks covered by the patterns. The extension makes updates effortless. AVOID IF: you require highly custom file grouping logic or work in niche ecosystems not covered by existing patterns (though you can always fork and extend). MONITOR IF: you're deciding between this and rolling your own patterns—the project's longevity is solid, but it requires no complex dependencies, so custom config is also viable as a fallback.
Independent dimensions
Mainstream potential
3/10
Technical importance
4/10
Adoption evidence
4/10
- Dependency on VS Code version compatibility—nesting feature requires v1.67+, limiting adoption to relatively recent VS Code installations.
- Opinionated patterns may not suit all teams; organization preferences vary and there is no granular per-language or per-framework override UI in core VS Code.
- Limited discoverability—most developers may never know this feature exists, capping potential audience.
- Maintenance burden as new frameworks and tools emerge; patterns must be actively curated or they become stale.
- No official VS Code involvement; project relies on one maintainer's continued interest and availability.
Likely to remain a stable, niche utility with slow organic growth. Adoption will remain concentrated among developers who actively explore VS Code's configuration options. As more frameworks and AI tooling emerge, the project will continue receiving incremental pattern updates, but mainstream adoption is unlikely given that file nesting remains a 'nice-to-have' feature, not essential.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- JavaScript
- License
- MIT
- Last updated
- 2w ago
- Created
- 53mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Autofix.ci App Not Installed
Some types files are not being nested
Support external config file for explorer.fileNesting.patterns
Support benchstat _bench_test.go naming convention
Breaking change notification
Top contributors
Recent releases
Similar repos
microsoft/vscode-eslint
This is the official VS Code extension that integrates ESLint into the editor,...
alefragnani/vscode-project-manager
Project Manager is a VS Code extension that helps developers quickly access and...
antfu/eslint-config
A personal ESLint configuration preset by Anthony Fu that provides opinionated,...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
antfu/vscode-file-nesting-config
this
|
3.7k | +2 | JavaScript | 7/10 | 2w ago |
|
microsoft/vscode-recipes
|
6k | — | JavaScript | 6/10 | 3mo ago |
|
microsoft/vscode-eslint
|
1.9k | — | TypeScript | 8/10 | 1w ago |
|
alefragnani/vscode-project-manager
|
2.6k | — | TypeScript | 8/10 | 3d ago |
|
antfu/eslint-config
|
6.2k | — | JavaScript | 8/10 | 2w ago |
|
microsoft/vscode-generator-code
|
1.6k | — | JavaScript | 7/10 | 1w ago |
Broader VS Code guidance and snippets; this project is narrowly focused on file nesting patterns only. Recipes are more general, nesting-config is deeper in one specific feature.
Projects can define their own patterns; nesting-config provides a curated starting point to avoid per-team configuration work, especially valuable for teams adopting VS Code across mixed tech stacks.
Similar intent (organize explorer view), but those typically add features beyond nesting. This project leverages VS Code's native feature, making it zero-dependency and lightweight.
