microsoft / microsoft/vscode-containers
Get rid of `fs-extra` in favor of VSCode's `fs` API
Open
Nobody has claimed this yet.
engineering
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 87
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 9
Description
Or use AzExtFsExtra which provides the same things using the VSCode fs API.
This is more compatible with Codespaces and would be a required step toward potentially having the extension run client-side, a la github.dev.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating all fs-extra imports and dependency references, then compare the needed operations with VS Code's fs API or AzExtFsExtra. Done means the extension no longer depends on fs-extra while preserving its current filesystem behavior and improving Codespaces compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100