docs: add more information about wasmtime caching#863
Merged
zshipko merged 1 commit intoextism:mainfrom Jun 18, 2025
Merged
Conversation
zshipko
approved these changes
Jun 18, 2025
Contributor
zshipko
left a comment
zshipko
left a comment
There was a problem hiding this comment.
This looks great, thank you!!!
This was referenced Aug 18, 2025
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.
Hello,
I encountered an error when trying to enable caching in my project, I could not compile any Plugins due to a bad configuration file used by the wasmtime crate (
failed to parse config file). I managed to find understand the error after seeing some changes made by wasmtime and its documentation. I was simply missing theenabledkey from the configuration, that has been removed fromwasmtime(and its cache sister crate).So I added more information in the README regarding this specific issue, and some extra behaviour that I noticed would happen regarding caching configuration.
Hopefully this is helpful!