feat: add fsCache option to improve build performance
#56
Conversation
This file contains 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
✅ Deploy Preview for twoslash ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
I think it would be fine to set to |
antfu
changed the title
fsCache option to improve build performance
antfu
approved these changes
Sep 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds
fsCacheoption that makes FS requests to be cached.When this flag is enabled,
vitepress buildin vitejs/vite gets 2x speed up.I made the default to be
falseso it needs to be set totrueby@shikijs/vitepress-twoslashfor build. That said, I didn't find a way to know whether it is dev mode or build mode inShikiTransformertype. Adding a way to know that might be also needed.