figwheel-start!
so that they don't return the SystemMap
as this was behaving badly in various REPL configurations 28e03affigwheel-sidecar.repl/get-project-cljs-builds
and deprecated(build-once)
work for builds that aren't opt none(clean-builds)
work for builds that aren't opt none:cljs-build-fn
figwheel option.clj
or .cljc
macro reloadingcljs.build.api/build
:recompile-dependents
default value bringing it inline with cljs compiler defaults:nrepl-middleware
server configuration has been added (see readme)
Thanks to Okke Thijhuis @otijhuis, give him a shout out!:ring-handler
a var so it picks up changes - thanks to @nikitonsky(figwheel.client/toggle-autoload)
or figwheel.client.toggle_autoload()
in the dev console:foreign-libs
, :libs
and Google Closure libs in your :source-paths
that follow Clojure
namespacing conventions - this is hot!(require ... :reload)
and (require ... :reload-all)
work correctly now:reload-dependents
client config parameter. It forces the "reloading"
of files that are dependent on changed files. This is very fast operation and can
potentially obviate the need for ^:figwheel-always
figwheel.connect
works:server-ip
server config option to all folks to not
default to binding "0.0.0.0" which exposes the connection to the network:devcards
option to figwheel client config, more on this later:websocket-host :js-client-host
option to allow the client to use the location.host
of
the loaded page. Thanks to @peterschwarz[cider-nrepl 0.9.0]
a little more easilyreload-config
special-fn in the repl:figwheel
is
set in the build(reset-autobuild)
REPL command now reloads the build config
from your project.clj
:optimizations
, :output-to
, :output-dir
:fighweel true
to builds that you want
figwheel to run on. The client code will be injected to the build.
You can inspect the generated client code in
target/figwheel_temp/<build id>/fighweel/connect.cljs
:false
starts two compile processes:id
caused NPE^:figwheel-always
was causing a double file reload when editing the marked ns:modules
configurations was
preventing figwheel from starting:nrepl-port
along
with a port number to the :figwheel
config in your project.clj will
start an nREPL server into the running figwheel process.
https://github.com/bhauman/lein-figwheel/wiki/Using-the-Figwheel-REPL-within-NRepl:autobuild
to false
will disable
the automatic loading of code on file changes. Now that the cljs REPL
development experience is maturing it's nice to have the option to do
REPL only development. Its a client side option so that you can change
back and forth between the styles of development fairly easily.:recompile-dependents
is false
:url-rewriter
client config option shouldn't be
needed in most cases now. If you are currently using :url-rewriter
it will
be broken as the form of the url argument is changing.:on-jsload
but just having app restarting/rerendering code
(like React.render
) at the bottom of your root application file.^:figwheel-always
can now be added as meta data to cljs namespaces that
you want to be reloaded whenever there is a file change in your source
tree. With this flag you won't really need :on-jsload
, even for complex
setups. Namespaces marked figwheel-always
do not have to be required.
So you can put this on your test runner namespace and viola!, you will have
your tests running in the client env on every reload. Pretty cool.cljs.user
ns after refreshing the browser.:debug
is a new client config option, when it is truthy figwheel
will print out copious amounts of debug information.:load-unchanged-files
is a client option that if set to false
will cause
the client to not reload files that haven't changed. With this option set to
false
files will only load if their content has changed. This option defaults
to true
.(in-ns 'your.cljs.namespace)
and poke around$ rlwrap lein figwheel
you can install rlwrap on OSX with brew: brew install rlwrap
:repl false
in the :figwheel
config:server-logfile
in
:figwheel
config:notify-command
, figwheel now honors
:notify-command
only on successful compiles, this should be especially helpful to
those who are using :notify-command
to run testsorg.clojure/clojurescript "0.0-2665"
or greater(ns ^:figwheel-load example.core
(ns ^:figwheel-no-load example.setup
:load-warninged-code true
in the figwheel clientdefonce
macro. It is built into cljs:heads-up-display false
in the client configemacsclient
or your editor's equivalent working correctly.
In the :figwheel
configuration in your project.clj
you need to include
an :open-file-command
option. This should be the name of a script on your
path that takes a file and a line number. The reccomendation here is to write
your own script and put it in ~/bin.:open-file-command
is emacsclient
aware so you can just provide "emacsclient"
as an option and it will just work.46 commits and many more changes
defonce
and not ClojureScriptsCan you improve this documentation? These fine people already did:
Bruce Hauman, bhauman, aJchemist & Colin YatesEdit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close