Liking cljdoc? Tell your friends :D

leiningen.figwheel


_figwheel-version_clj

source

_rebel-readline-cljs-version_clj

source

auto-clean?clj

(auto-clean? project)
source

build-onceclj

(build-once project build-ids)
source

builds-to-start-build-idsclj

source

check-configclj

(check-config project)
source

clean-build-idsclj

source

clean-idclj

(clean-id id)
source

clean-idsclj

source

clean-on-dependency-changeclj

(clean-on-dependency-change {:keys [target-path dependencies] :as project})
source

cljs-buildsclj

(cljs-builds data)
source

command-like?clj

(command-like? command)
source

command?clj

source

coord-versionclj

(coord-version library)
source

create-config-sourceclj

(create-config-source project config-source-data)
source

ensure-build-dirsclj

(ensure-build-dirs proj)
source

eval-and-catchclj

(eval-and-catch project requires form)
source

fig-dispatchcljmultimethod

source

figwheelclj

(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
sourceraw docstring

figwheel-ednclj

(figwheel-edn)
source

figwheel-edn-exists?clj

(figwheel-edn-exists?)
source

figwheel-exec-bodyclj

(figwheel-exec-body body)
source

figwheel-mainclj

(figwheel-main project build-ids)
source

figwheel-optionsclj

(figwheel-options data)
source

fuzzy-config-from-projectclj

(fuzzy-config-from-project project)
source

intersect-not-emptyclj

(intersect-not-empty & args)
source

known-commandsclj

source

launch-figwheelclj

(launch-figwheel command project build-ids)
source

make-subprojectclj

(make-subproject project paths-to-add)
source

map-to-vec-buildsclj

(map-to-vec-builds builds)
source

named?clj

(named? x)
source

needs-profile-merging?clj

(needs-profile-merging? project)
source

normalize-dataclj

(normalize-data data build-ids)
source

on-stamp-changeclj

(on-stamp-change {:keys [file signature]} f)
source

opt-none-build-idsclj

(opt-none-build-ids {:keys [all-builds]})
source

opt-none-build?clj

(opt-none-build? build)
source

(print-suggestion thing things)
source

project-keys-affected-by-profile-meringclj

(project-keys-affected-by-profile-mering project)
source

rebel-readline-cljs-versionclj

source

report-if-bad-build-idclj

(report-if-bad-build-id known-build-ids build-id)
source

report-if-bad-build-idsclj

(report-if-bad-build-ids project build-ids)
source

report-if-bad-build-ids*clj

(report-if-bad-build-ids* known-build-ids build-ids)
source

report-if-bad-commandclj

(report-if-bad-command command)
source

run-build-onceclj

(run-build-once project config-source-data paths-to-add build-ids)
source

run-config-checkclj

(run-config-check project config-source-data options)
source

run-figwheelclj

(run-figwheel project config-source-data paths-to-add build-ids)
source

simple-apply-lein-profilesclj

(simple-apply-lein-profiles project)
source

simple-merge-works?clj

(simple-merge-works? project)
source

source-paths-for-classpathclj

(source-paths-for-classpath {:keys [figwheel-options all-builds build-ids]
                             :as data})
source

suggest-likeclj

(suggest-like thing things)
source

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close