This repository has been archived by the owner on Jul 2, 2022. It is now read-only.
Compatibility fixes: --reagent and lein figwheel #248
Closed
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.
There's a bunch of existing documentation out there that starts with a
lein new chestnut
, and so we should try not to break existing invocations and uses. Eventhough
--reagent
is now the default, it should still be possible to specifythe flag.
We should also make sure that
lein figwheel
continues to work. Normally westart figwheel as part of the system, but sometimes people use Chestnut only for
the figwheel/clojurescript part, and in that case they might only care about
running Figwheel. Since we write our compiled js to dev-target/public, we should
make sure dev-target is on the classpath so the Figwheel web server can find it.