Add cache-dir option to avoid running shadow server conflicts #23
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.
If you have another running
shadow-cljs
instance running, like for your main app, or run Jest before running the main app, the second will err complaining that another instance is running. This PR fixes that by setting thecache-dir
to.jest/shadow
(although it doesn't seem to actually change anything except whereshadow-cljs
looks for an openhttp.port
and etc. files).