(auto-clean? project)
(build-once project build-ids)
(check-config project)
(clean-id id)
(clean-on-dependency-change {:keys [target-path dependencies] :as project})
(cljs-builds data)
(command-like? command)
(coord-version library)
(create-config-source project config-source-data)
(ensure-build-dirs proj)
(eval-and-catch project requires form)
(figwheel project & command-and-or-build-ids)
Figwheel - a tool that helps you compile and reload ClojureScript.
Refer to the README at https://github.com/bhauman/lein-figwheel
Figwheel commands usage:
The common way of invoking Figwheel looks like this:
lein figwheel build-id build-id ...
The above will run the default Figwheel :reactor command. See below for a description.
lein figwheel [command] build-id build-id ...
Will execute the given [command] on the build-ids supplied. A [command] always starts with a ":" and should be one of the following.
Commands:
:reactor build-id ...
If no [command] is supplied then this command will be chosen by default.
This command will start a Figwheel autobuild process, server and repl based on the supplied configuration. It will start autobuild processes for all the build-ids supplied on the command line
The build-id supplied must exist in your configuration. If no build-ids are supplied, Figwheel will pick the first build in your config with :optimizations set to nil or :none.
You can customize witch builds are started by default, by setting the :builds-to-start key n your config to a vector of the builds you want to start. Example:
:figwheel {
:builds-to-start ["example"]
}
The Figwheel system will watch your ClojureScript files for changes. When your files change Figwheel will compile them and attempt to notify a Figwheel client that these changes have occurred
:check-config
This will run a validation check on your configuration.
All arguments supplied to this command will be ignored.
:once build-id ..
This will build all the supplied builds once. No autobuilder or watching process will be launched. If no build-ids are supplied this command will build all the builds in your config.
The Figwheel ClojureScript will not be injected into any of these builds.
:help
Prints this documentation
Configuration:
Figwheel relies on a configuration that is found in the project.clj or in a figwheel.edn file in your project root. If a figwheel.edn is present any Figwheel configuration found in the project.clj will be ignored.
To learn more about configuring Figwheel please see the README at https://github.com/bhauman/lein-figwheel
Figwheel - a tool that helps you compile and reload ClojureScript. Refer to the README at https://github.com/bhauman/lein-figwheel Figwheel commands usage: The common way of invoking Figwheel looks like this: lein figwheel build-id build-id ... The above will run the default Figwheel :reactor command. See below for a description. lein figwheel [command] build-id build-id ... Will execute the given [command] on the build-ids supplied. A [command] always starts with a ":" and should be one of the following. Commands: :reactor build-id ... If no [command] is supplied then this command will be chosen by default. This command will start a Figwheel autobuild process, server and repl based on the supplied configuration. It will start autobuild processes for all the build-ids supplied on the command line The build-id supplied must exist in your configuration. If no build-ids are supplied, Figwheel will pick the first build in your config with :optimizations set to nil or :none. You can customize witch builds are started by default, by setting the :builds-to-start key n your config to a vector of the builds you want to start. Example: :figwheel { :builds-to-start ["example"] } The Figwheel system will watch your ClojureScript files for changes. When your files change Figwheel will compile them and attempt to notify a Figwheel client that these changes have occurred :check-config This will run a validation check on your configuration. All arguments supplied to this command will be ignored. :once build-id .. This will build all the supplied builds once. No autobuilder or watching process will be launched. If no build-ids are supplied this command will build all the builds in your config. The Figwheel ClojureScript will not be injected into any of these builds. :help Prints this documentation Configuration: Figwheel relies on a configuration that is found in the project.clj or in a figwheel.edn file in your project root. If a figwheel.edn is present any Figwheel configuration found in the project.clj will be ignored. To learn more about configuring Figwheel please see the README at https://github.com/bhauman/lein-figwheel
(figwheel-edn)
(figwheel-edn-exists?)
(figwheel-exec-body body)
(figwheel-main project build-ids)
(figwheel-options data)
(fuzzy-config-from-project project)
(intersect-not-empty & args)
(launch-figwheel command project build-ids)
(make-subproject project paths-to-add)
(map-to-vec-builds builds)
(named? x)
(needs-profile-merging? project)
(normalize-data data build-ids)
(on-stamp-change {:keys [file signature]} f)
(opt-none-build-ids {:keys [all-builds]})
(opt-none-build? build)
(print-suggestion thing things)
(project-keys-affected-by-profile-mering project)
(report-if-bad-build-id known-build-ids build-id)
(report-if-bad-build-ids project build-ids)
(report-if-bad-build-ids* known-build-ids build-ids)
(report-if-bad-command command)
(run-build-once project config-source-data paths-to-add build-ids)
(run-config-check project config-source-data options)
(run-figwheel project config-source-data paths-to-add build-ids)
(simple-apply-lein-profiles project)
(simple-merge-works? project)
(source-paths-for-classpath {:keys [figwheel-options all-builds build-ids]
:as data})
(suggest-like thing things)
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close