Expose ts.matchFiles as public API to make implementing readDirectory easier.
See original GitHub issueProblem:
When implementing a custom host that virtualizes the file system, the readDirectory
method is cumbersome to implement in a way that matches tsc behavior.
If you look at the hosts within typescript, the matchFiles
method was added to unify behavior with readDirectory
between hosts.
While matchFiles
is exported, it isn’t in the type definition files so I’m assuming it is “private” API.
Either the host should be able to provide a getFileSystemEntries(path: string) => { files: string[], directories: string[] }
to get a readDirectory
implementation or expose matchFiles
.
I’m working on improving the broccoli-typescript-compiler
broccoli plugin to have more parity with tsc and VS Code, but I need to virtualize the FS, since broccoli builds from tmp directory and I want the node_modules/@types discovery, tsconfig extends, etc all to work, I need to pretend the tmp dir is inside the project.
Thanks
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:10 (3 by maintainers)
Top GitHub Comments
@AviVahl I’m trying to do the same thing and just encountered
readDirectory
myself. My goal is to publish an in-memory implementation ofts.System
for use in browsers demos, experiments, etc. Do you have a link to what you’re working on?I’m currently having to implement a readDirectory etc and I was really hoping this had been addressed 3 years ago when brought up.