Im trying to get started with shadow cljs and im using the re-frame example

The example works beautifully, and with the skeleton project.clj cursive picks everything up just fin

but when I try to use semantic-ui-react I get a "Uncaught ReferenceError: require is not defined"

I am running through yarn watch

@thheller Yesterday's problem shadow-cljs watch app slow appear again: it takes a long delay before each of two Cache write: xxx/xxx.cljs , but the times are not reported.

shall I update the version of shadow-cljs first? 2.2.26 now

updated to 2.3.0

@emccue you are using ancient versions in the project.clj. definitely upgrade all of them before continuing.

latest shadow-cljs is 2.3.0

maybe because during shadow-cljs watch app1, I shadow-cljs release app2 (another app)?

@cmal not really. each build has its own cache directory so they don't interfere with each other

there could be one possible problem looking at the code

do you use cljs.spec in both apps?

only in one

not in the slow app.

app1

I will keep one eye on this problem, and try to figure out what happens when it becomes slow.

currently the cache-write only logs when it completed, not when it started so I assume that the cache write itself is just slow since its not timed

the cache is potentially writing a lot of data.

can you check how large the .shadow-cljs/builds/app1/dev/ana/your/ns.cljs.cache.transit.json is?

maybe it is getting excessively large for some reason

are you maybe running low on disk space? the OS might get into real trouble with the FS then

du -sh 33M

hmm thats normal

in /builds

Free disk space 15.8GB

its SSD

hmm yeah thats all ok then

I will expand the timing log for cache reads/writes so get more accurate infos about that

but still not a clue what could be causing this

OK. I'll keep on my using and see what happens when it becomes slow.

Thank you so much.

How can I use alternative artifacts providing the same namespaces and API in dev and production, e.g. day8.re-frame/tracing and /tracing-stubs?

In leiningen it's generally done different :dependencies in each profile but that doesn't seem possible in shadow-cljs. Am I missing something?

^done with

@clojurians.net I think this approach is pretty terrible and yes with just standard shadow-cljs this is not possible

you can do it if you use lein or deps.edn

I will look into what exactly the re-frame trace stuff is doing and see if there isn't an alternative way

There's also https://github.com/philoskim/debux-stubs I'm not a great fan of it either, but it strikes me as the most reliable way to make sure that tracing/debugging code doesn't end up in a production build. It is theoretically possible to leverage Closure's dead code elimination for that, but I believe there have been issues with it in the past and it's quite a bit more messy and error prone.

devcards does this via :devcards true. this seems more suitable since its just a compiler options.

I would not trust DCE fully either

the macro stuff could just eliminate based on the compiler setting

Yeah that does sound cleaner. In the meantime, for projects that do it the other way, I'm guessing this would be the way to go: lein with-profile +<dev/prod> run -m shadow.cljs.devtools.cli ...

yes

Great, thank you.

@thheller it was an obvious fix but it worked, thank you

@emccue how come you picked that particular version? is it still used in an example somewhere?

Is it possible to use preloads with :target npm-module?

Yeah it was used in whatever example I pulled this from

ooh

it is in the example project.clj

...somewhere

crap

I dont know

@colindresj no since there is no clearly defined entry they should be preloaded for

@thheller According to the shadow-cljs docs, i should be able to copy the some fulcro source file, place it in my own project matching the directory structure of where it would’ve been were it in fulcro, make some change, and it would be using that instead of the actual lib. It seems this file is being ignored. Are there any known gotchas about this? I’m specifically trying to work on fulcro.client.primitives.cljc. I’ll be going off to bed now. Dropping this message hoping to catch you during your day, because timezones.

@levitanong you mean fulcro/client/primitives.cljc

slashes not dots

and yes if you put it into your classpath like that it should work

That’s what I thought @thheller. Any idea how I might integrate https://github.com/Day8/re-frame-10x into a storybook build?

@colindresj not sure what a storybook build is, but there’s an example of this usage on https://github.com/jacekschae/conduit

Storybook’s is a kind of like a react component dev environment @danielcompton. It’s a JS lib though, so I’ve been using the npm-module shadow target to get my cljs code to work with it, but now want to include re-frame-10x and I’m having a little trouble

I tried just requiring the compiled re_frame_10x.preload namespace, but it I get some react rendering errors when doing that, something about vbox not returning a valid component

@colindresj I don't remember if it was possible to influence which files storybook loads. IIRC it is just looking for files with a regexp

you could probably just require re-frame-10x.preload in your stories namespace?

Yeah, that’s what I did

@danielcompton https://clojureverse.org/t/using-storybook-with-cljs/1495

And namespace-wise everything seems good, but then I run into that react rendering errror, so I feel like something’s up

did you set the proper :closure-defines?

Yeah, and just for testing I removed it and got the 10x warning telling me to set closure defines

So, I think that part’s good

hmm maybe something in re-frame-10x doesn't like how storybook loads the code?

That’s what I’m thinking, or vice versa

For reference, this is my error @danielcompton Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. Check the render method of day8.re_frame_10x.utils.re_com.v_box

@colindresj have you chosen the right version of re-frame which matches your React version?

If you can't get it working, open an issue with a reproduction

Ok, will do. Thanks