I'm trying to js/require a json but I can't figure out which path the js/require is starting at, how can I find out?

mhm maybe it doesn't make sense looks like I got the path right as it works for images, for instance (js/require "../resources/images/ui/welcome.jpg") works but (js/require "../resources/images/ui/fleets.json") doesn't

I'm unable to load the kaocha repl using (use 'kaocha.repl) in my shadow-cljs repl. I have added it in the dependencies like so:

:dependencies [[lambdaisland/kaocha "1.0-612"]]

Error in phase :compilation
Only [lib.ns :only (names)] and optionally `:rename {from to}` specs supported in :use / :use-macros; offending spec: [kaocha.repl] at line 1 cljs/user.cljs

kaocha is not supported currently

also the (use 'kaocha.repl) are instructions for CLJ not CLJS

@thheller what's a good way to automate tests with shadow and maybe cider?

no clue. I don't use tests in CLJS.

@thheller I’ve got a css generated from outside the directory of where I’m working using SASS. The generation works fine, but shadow-cljs does not reload. When I manually edit the generated CSS file shadow-cljs reloads. Any idea on how to solve this?

you mean if you edit the generated file it reloads but it doesn't reload when it is generated?

Yes

weird, no idea

what do you use to generate?

gulp

check if the file last-modified timestamp is changed when that generates a new file?

sure

It updates, but to two hours back in time

hmm might be that shadow-cljs uses the wrong check?

usually it should just check (not= last-mod prev-mod)

not (> last-mod prev-mod)

Hmm.. seems like gulp sets the last-modified timestamp to UTC+0

I’m currently at UTC+2

Oh well

it should be enough if it changes, which direction it changes shouldn't matter

hmm yeah dunno. might be something internal from the filewatcher that it doesn't like things going back in time?

shadow-cljs doesn't care

just teach gulp to set the correct date 😉

Is there a trigger based on changed files?

Ie, a notify from a java api

which OS do you use?

If so, could be that one that doesn’t report a changed file since it’s backwards in time. Ie, a previous version?

MacOS

hmm… shouldn’t matter though

it does

macos uses the hawk library to watch fs changes

linux/win do not

dunno about hawk

Coolies

That did the trick

So weird though

I have a RN app with minimal shadow-cljs config and it compiles as I expect. Auto load is not working however and I’m not sure where to look, does anybody have any ideas?

# shadow-cljs.edn
{
 ...
 :builds {:dev {:target     :react-native
                :init-fn    env.main/main
                :output-dir "target/dev"
                :devtools   {:autoload true
                            :after-load my.core/print-debug-stmt}
 ...
}

Running shadow-cljs v2.8.99 with npx shadow-cljs watch :dev

is this my.core/print-debug-stmt maybe not included in the regular build?

may need to add :preloads [my.core] into :devtools so the ns is actually compiled?

Hello everyone, I’m new to shadow-cljs and ClojureScript. I was curious if there is a command that audits your dependencies for new available releases, and if there’s a command to update dependencies as well? Thanks for all the help!

there is not (yet) a command for that no if you are using shadow-cljs.edn only. lein or deps.edn have options for that.

npx npm-check -u for npm deps

https://github.com/Olical/depot for clj(s) deps

if you’re using deps.edn

lein-ancient if lein

Question for anybody who uses cljs-devtools (https://github.com/binaryage/cljs-devtools) I just added it to my basic reagent/re-frame project deps.edn

{:paths ["src"]
 :deps  {thheller/shadow-cljs {:mvn/version "2.8.94"}
         binaryage/devtools   {:mvn/version "1.0.0"}
         reagent              {:mvn/version "0.10.0"}
         re-frame             {:mvn/version "0.12.0"}}}

{:deps   true
 :builds {:app {:target     :browser
                :output-dir "public/out"
                :modules    {:app {:entries []
                                   :init-fn 
                :devtools   {:http-root "public"
                             :http-port 8020}}}}

failed to load shadow.module.app.append.js TypeError: alpha_journal.app.render is not a function
    at Object.alpha_journal$app$main [as main] (:8020/js/cljs-runtime/alpha_journal.app.js:15)
    at eval (:8020/js/cljs-runtime/shadow.module.app.append.js:4)
    at eval (<anonymous>)
    at Object.goog.globalEval (app.js:836)
    at Object.env.evalLoad (app.js:2224)
    at app.js:2414
DevTools failed to parse SourceMap: 
...

check the first error? alpha_journal.app.render is not a function this is likely the result of something else failing before it

@thheller :face_palm: thanks, accidentally slurped my render function into another function. That fixed my rendering issue, but now I’m still getting the sourcemap parsing failures:

DevTools failed to parse SourceMap: 
DevTools failed to parse SourceMap: 
DevTools failed to parse SourceMap: 
DevTools failed to parse SourceMap: 
DevTools failed to parse SourceMap: 
DevTools failed to parse SourceMap: 
...

(ns 
  (:require
   [reagent.core :as r]
   [reagent.dom :as dom]))

no you shouldn't have a direct require for it anywhere. thats already taken care of just by including it in your dependencies

is the path correct? I mean what do you get when you open http://localhost:8020/js/cljs-runtime/goog.debug.error.js.map manually?

I get a blank page and console output as:

Failed to load resource: the server responded with a status of 404 (Not Found)
app.js:1 Failed to load resource: the server responded with a status of 404 (Not Found)
app.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
DevTools failed to parse SourceMap: 
DevTools failed to parse SourceMap: 

so its not the correct path?

where is your output?

Sorry I’m a bit lost on the path situation. I’m seeing my page render on http://localhost:8020/, but if I follow the sourcemap warning link (ex. http://localhost:8020/js/cljs-runtime/goog.async.workqueue.js.map) I get a blank page and in the console, I get that output that I wrote above

what is your :output-dir? what is your :asset-path? what is the path you are loading your JS from in your HTML?

Hmm don’t believe I have those explicitly set. This is my shadow-cljs.edn

{:deps   true
 :builds {:app {:target     :browser
                :output-dir "public/out"
                :modules    {:app {:entries []
                                   :init-fn 
                :devtools   {:http-root "public"
                             :http-port 8020}}}}

so you need to add :asset-path "/out" (right after :output-dir) since that defaults to /js

you can skip :entries [] since :init-fn already implies that

Awesome, so if I understand correctly, when I have a custom :output-dir I should remember to set my :asset-path (otherwise it uses the default path which is wrong) That seemed to clear up most of my sourcemap warnings. I just have a preload and postload warning?

don't know what those are? are you working on a browser extension? those errors come from a browser extension?

Got it. Turned out Adblocker causes those warnings. If anyone else runs into the same thing, I just removed my adblocker extension.

@thheller thanks for all the help! Much appreciated 🙂 I was curious though if you could elaborate a bit on what :entries does. Some of the config keys have been confusing me since I’ve been following a lot of tutorials and examples but a lot of them have very different config layouts in their shadow-cljs.edn. Thanks!

entries is the namespaces that should be included in the module (your build basically)

:init-fn basically is sugar for :entries [] and calling the main fn on load

you can keep it but it is redundant

Awesome, thanks for the clarification. Helps a lot

is there a way to import a cljs library from a github repo instead of a maven repo? I need to patch the https://github.com/ckirkendall/kioo library

if you use deps.edn, it’s fairly easy

requires moving your dependencies from shadow-cljs.edn to a deps.edn

alternatively, you can copy + paste the kioo source files into your project

https://shadow-cljs.github.io/docs/UsersGuide.html#deps-edn

@lilactown deps.edn won't work. the lib has no deps.edn.

you’re right, I didn’t think of that. if they’re forking it anyway, it’s easy to add one

true

I use lein project.clj and shadow-cljs.edn