Allow node VFS based programmatic usage #2392
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there folks, I ended up wanting to replace some code where I was making a folder in
/tmpto run the schema generator over and thought I should see if anyone else had looked at a vfs only to find that I had the answer for myself #2182So, I figured I should add support. This adds a new config variable which accepts a
ts.Programso you can set up the TS environment however you like (e.g. for vfs support, like I have provided as a test)While I was there, I asked Claude Code to generate JSDoc comments for the config to make programmatic usage more useful - but if that's annoying, I can drop them.