Dieter Komendera

We're using `boot-cljs-repl` right now, and we're running into https://github.com/adzerk-oss/boot-cljs-repl/issues/49, so I'm looking to use the figwheel repl now.

Another alternative I see is to add another task, like maybe `cljs-test-resources` which adds meta data to files in the fileset with `add-meta` and the `run-cljs-tests` finds those marked files...

Using `0.3.1-hardlinks-SNAPSHOT` I get an error when it tries to create the link: ``` $ boot backend-test Adding: ([doo "0.1.7"]) to :dependencies npm WARN [email protected] requires a peer of react-dom@^0.14.0...

The error seems to happen when `:resource-paths` points to a subdirectory: This errors: ``` :resource-paths ["clj/backend/fixtures"] ``` Moving `fixtures` up to the project root doesn't error: ``` :resource-paths ["fixtures"] ```

@crisptrutski doesn't work as expected for me. I've adapted `link-resources!` to work for me like this: ```clojure (defn link-resources! [dir] (when (.exists (io/file "node_modules")) (file/sym-link (.getAbsoluteFile (io/file "node_modules")) (io/file dir...

So I don't understand why `run-tests!` has to manage the resources itself: In `add-suite-ns!`'s `commit!` the fileset is written to the directory already. And the fileset includes my fixture resources,...

I guess this is basically the same as https://github.com/clojure-emacs/clojure-mode/issues/433

While I haven't ran into that specific issue, I'd like to note that the current Slate externs won't work for advanced compilation. The current externs are generated, but they are...

@RyanBertrand I ran into the same issue when packaging Slate and ended up using https://unpkg.com/. See https://github.com/cljsjs/packages/blob/f62ea137dae2c79fa9dd0e9198d40a895761d2f6/slate/build.boot#L21

Looking into `boot.core` I noticed that the `last-file-change` atom is no longer being updated in the boot instance where `watch` stopped working.