Enable Node.js compile cache on CLI when module.enableCompileCache() is available
#624
+55
−0
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
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.
Node.js v22.8.0 and later have been supported
module.enableCompileCache(), to enable V8 compile cache. This PR adds the patch process to apply compile cache in early.Effectively this is retry of #139.
v8-compile-cachehad been removed in #521 due to incompatibillity with ES Modules.Benchmark of
time ./marp-cli.jsin my environment shows x1.22 speed up. (Use average time of 10 executions)mainenable-compile-cacheNote
The compile cache would not be enabled when Marp CLI was executed from Node.js API.