One possible way is, in src/main of your project, create a symlink to the src directory of the local dep, e.g. src/main/foo where foo is a link to ~/dev/foo-project/src/foo

Or if you use emacs, you can simply link a buffer of the local dep project to the cider session of your own project, so you can modify the source of the local dep project, and eval it in your repl

another way if you use deps.edn is :local/root

{:paths ["src" "resources"]
 :deps {com.fulcrologic/fulcro {#_#_:mvn/version "3.0.3"
        ....                        :local/root "/Users/me/fulcro"}
        lilactown/hx {:mvn/version "0.5.3"}}}

maybe there's something i need to run as part of the command i use to kick off shadow-cljs? at the moment i run npx shadow-cljs watch app

it looks fine to me. maybe try without ?cache-buster? your webserver just may be caching to aggressively too and only serving the "old" content when another request is made?

or maybe you configured something in the wrong place?

kinda hard to tell without seeing your config

it all looks correct from what you described

yeah i thought it might be the cache-buster but that doesn't make a difference

here's my config

{:lein {:profile "+dev"}
 :builds
 {:app {:target :browser
        :output-dir "resources/public/js/compiled/"
        :asset-path "/js/compiled"
        :compiler-options {:infer-externs :auto}
        :dev {:compiler-options {:closure-defines
                                 {"day8.re_frame.tracing.trace_enabled_QMARK_" true
                                  "re_frame.trace.trace_enabled_QMARK_" true}}
              :devtools {:preloads [day8.re-frame-10x.preload]
                         :after-load user/after-load
                         :watch-dir "resources/public"}
              :external-config {:devtools/config {:features-to-install :all}}
              :pretty-print true
              :print-input-delimiter true
              :source-map true}
        :release {:compiler-options {:closure-defines {goog.DEBUG false}
                                     :optimizations :advanced}}
        :main cue.core
        :modules {:cue {:entries [cue.core]}}}}}

sorry trying to make it more legible

:external-config needs to be in :compiler-options otherwise it has no effect

pretty-print and source-map default to true and would other also need to be in :compiler-options

oh cool thanks

:main cue.core does nothing

other than that it looks fine

yeah i don't think i've gone crazy here. ok could it be the way i run shadow, which is with this?

(require
  '[orchestra.spec.test :as stest]
  '[shadow.cljs.devtools.api :as api]
  '[shadow.cljs.devtools.server :as server])
(server/start!)
(api/watch :app)
(api/repl :app)
(stest/instrument)

do i need to run something else to kick off the file watcher?

nope thats it

did you check the browser console/devtools? does it try to request css?

you can also set :log {:level :debug} in shadow-cljs.edn top level

that will log a bunch of extra stuff, including changed css files it found

i'll try that. no, i'm seeing nothing about css in the console, i'm pretty sure it's not watching for changes

no, there's no output on css compilation

it is independent and has nothing to do with CLJS compilation

yeah that makes sense, i wouldn't expect the two to be connected

although presumably there's some shared infra to push changes

hmm nevermind I just checked. must have removed the log messages

I don't get any either. css reload works though

am i right to have "resources/public" as the value for my :watch-dir when my css lives at resources/public/css/compiled?

and is served from /css/compiled/cue.css

basically you take watch-dir and append the path of the css

that should be the path in your filesystem

so resources/public + /css/compiled/cue.css

yeah makes sense.

my css compilation occurs in WSL, but shadow-cljs is runnign in windows. it's all on a windows filesystem though. could there be a problem with watching files on a windows filesystem?

actually i can test that by editing, and no, that isn't the problem

well, thanks for your help. the only way forward i can see is to stop using my webserver and pass my handler to shadow-cljs and see if i can get that working. much appreciated as ever!

the webserver isn't even involved in this so it should be working fine. I know its working for others too

but you never answered my question about what the browser devtools show?

I mean the request panel? does it do something?

you can also check if the websocket is receiving messages

no, there are no requests

should see messages like this one {:type :asset-watch, :updates #{"/css/foo.css"}}

oh yeah let me check that

no, i'm seeing only repl ping/pong

other than that I don't really know. I'm on windows too so that shouldn't be an issue

same deal running from a terminal inside wsl, so it's something to do with my project and not my environment

oh. i read in the docs that :watch-dir was only needed for non-webserver setups, but your comment about the webserver not being involved makes me wonder whether i misunderstood?

if you configure the built-in webserver it just implicitly also sets :watch-dir

nothing else to it

if you reproduce this in a simple project I can take a look

it is working fine for me so kinda hard to guess what might be going on for you

yeah sure, ta

I've stripped it down and have a small repro https://github.com/conan/css-reload

same deal. tested using cursive and the command line, in windows, wsl and on mac. i'd be super grateful if you had time to cast an eye, but obviously only if you're curious.

I rewrote the config to be

{:source-paths ["src/cljs"] 
 :dependencies
 [[reagent/reagent "0.8.1"]]
 :builds
 {:app {:target :browser
        :output-dir "resources/public/js/compiled/"
        :asset-path "/js/compiled"
        :compiler-options {:infer-externs :auto
                           :external-config {:devtools/config {:features-to-install :all}}}
        :devtools {:after-load user/after-load
                   :watch-dir "resources/public"}
        :modules {:css-reload {:entries [css-reload.core]}}}}}

css reload works fine after doing that

I have no clue why it doesn't work when running through lein

I don't have time right now to figure out why ... there are many things wrong with the config though

core.async version is too old

cljs version is too old

so I'm blaming some kind of dependency conflict on this

Amazing thanks!

Thanks. So say i just have a small app with 3 namespaces: main, a, b. main requires a and b. So in shadow-cljs.end the setup would just be:

:modules 
{:main {:init-fn some.app.main/-main}
 :a {:entries [some.app.a} :depends-on #{:main}}
:b {:entries [some.app.a} :depends-on #{:main}}}

some.app.main cannot require some.app.a or b directly

and some.app.a cannot require some.app.b directly

neither can b require a

thats pretty much it

some.app.main cannot require some.app.a or b directly Concretely, you mean you cannot have: (ns some.app.main (:require [some.app.a :as a]) ? You have to use the lazy load functionality?

yes

link to issue: https://github.com/Lokeh/helix/issues/1 link to JS code: https://github.com/Lokeh/helix/blob/master/src/helix/impl/class.js

fun right?

dunno what to do ...

is the ES6 code processed differently in browser vs RN?

ESM-CJS interop sucks big time

I’m happy to do something hacky for now

the issue is the ["react" :as react] is equiv of import * as react ...

so changing it to make import React work would break the CLJS parts too

hrm yikes

just to confirm though, import * as React should work in e.g. browsers right?

and what makes things worse it that this is an "upcoming" default ... meaning that most libraries have not adopted this yet

it’s only when doing CJS interop w/ RN?

so they would break too because they still expect import {createElement} from "react" or whatever to work

in the browser I can sort of control it better

but RN builds the JS parts so I kinda can't do much

or rather I dunno how to tell the closure compiler to "accept" this

so is it RN that is complaining about the glob syntax, or shadow-cljs, or closure?

don't think its even possible

closure complaining about what shadow-cljs gives it I guess

I honestly don't know why it works one way but not the other

I wonder if it’s because I’m running it from a REPL

let me actually build some code with it

you can use commonjs that is less problematic

but .. no advanced for those parts anymore then

hmm yeah, it compiles fine in my browser build. at least in dev mode

this is ~34 lines of code so I don’t think missing out on advanced compilation will be a big deal

I also doubt it will be used super often, as it’s only used to construct a React class which is only necessary when using error boundaries

so as long as it doesn’t “infect” other code too much with it’s lack of optimizations I am fine with switching to CJS

commonjs has other issues though ... it just sucks all around to be honest

I don't like the situation but I don't know what to do

yeah 😞

the way it works now has the "highest" compatibility with most packages

if I change something like 50% of them break

it'll be better when webpack v5 comes out and people adopt (since it will also break there)

well this seems to only be a problem when using npm packages inside of a JS file on the classpath

but dunno how long that'll be and don't know what fun kind of changes the closure compiler throws into the mix until then

it’s a shit show for sure 😞

@U05224H0W can you maybe transpile it differently and output it to different file extensions, i.e. native.js versus web.js

so is the syntax that is meant to work is this import * as react so that you can do this ["react" :as react] but react native isn't recognizing that syntax since it transpiles the JS itself (yet it has to be this way in es6 for the cljs import statement to work)

did I understand that correctly?

tried to test this out in helix but doesn't look like shadow-cljs recognizes the different platform extensions. in either case, maybe that could be a solution since react native will look for .native.js before .js

@lilactown actually what I'd suggest is not importing react at all in the .js file

you are just exporting a function anyways

so just pass Component as the first arg in the function

ah good idea

@U05224H0W has an article on code splitting cljs, maybe it's what you're looking for https://code.thheller.com/blog/shadow-cljs/2019/03/03/code-splitting-clojurescript.html

(ah I see it was linked in thread, nvm)