hi everyone. do we have a re-frame template for shadow-cljs? meaning something line lein new shadow-cljs +re-frame

the re-frame template uses shadow-cljs I think?

https://github.com/day8/re-frame-template

oh

nice 😄

thanks @thheller

@thheller so there are only two loader modes? :eval (default) and :script (old one)

yes

well :script technically has 2 modes

async and actual <script> tags, depending on whether you use <script async src="the-module.js"> or not

one uses document.write to add script tags, the other fetches files and evals them

so probably has the same issues as :eval. never tested.

I think both will work, the issue is probably that SHADOW_ENV.evalLoad is really running “anonymous” code which is not associated with any source file, so (logically) that source file is not created/tracked in the DevTools - devtools only creates “virtual” cljs files from sourcemap information (orange stuff in devtools resource tree)

loading the source via fetch and eval'ing it is just as "anonymous"

there is no way chrome ties the eval to the file it just fetched

ok, true

but just the fact that it fetched the url could add it into DevTools and cljs source reference would work

(my guess)

my guess is that it expects //# sourceURL= or something instead of just /js/cljs-runtime/foo.bar.js

I can't remember if I ever tried this in a browser context. I tried it in react-native and that didn't work at all since you don't know the location

I do remember that I played around with this a whole bunch ... wish I left more comments 😛

🙂 this stuff is still in flux, there used to be pretty bad bugs in devtools sourcemap implementation for example, so stuff could have changed since you last looked

thats possible too .. it has been 2 years or so since I implemented that

there are still issues between mapping locals, but it is low priorty for them to fix: https://github.com/binaryage/dirac/issues/53

yeah its pretty unreliable in some situations

here is the issue I have with breakpoints: https://github.com/binaryage/dirac/issues/64 is works only sometimes on simple code

it would help if cljs generated dev code on more lines (use more newlines to split logical js pieces like humans)

by now I've seen enough generated JS to know what the CLJS looked like 😛

I see, that is what I tend to do as well, but I have to see the js files in devtools 🙂

@thheller good news, your guess was correct changing sourceURL to full url fixed the issue in :eval mode for me

sorry, I didn’t understand it at first because whenever I saw sourceURL I thought I’m reading sourceMappingURL, so I didn’t get it

have to go, will updat the ticket later

should be an easy fix, I hope