VS Code users struggle to scope extensions to each project
Developers who use VS Code across different languages and projects want only the relevant extensions active, to reduce performance impact and clutter. Teams also want consistent extension setups across projects, while the reports say workspace recommendations do not provide on-demand loading and unloading. These requests date from 2018, so the remaining gap needs validation against VS Code’s newer profile features.
For developers and teams using VS Code across multiple projects. Mentioned from Jan 2018 to Jul 2018 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
My VS Code has tons of extensions, but some projects use only a small slice of those, so I don't see a reason why they should be enabled and slow everything down/create unnecessary cognitive load
Have in mind, that peoples uses VSCode for everything, so installing like 30 extensions to have PHP, TS, JS, etc, have performance impact. With this method we can load extensions which we actually need
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks