anyone know why this started popping up? could not find string alias for "socket.io-client" from app.client

@thheller ^

weird - I restart some of my builds and it went away

Cross posting from the CLJS Slack channel: https://clojurians.slack.com/archives/C03S1L9DN/p1545065495662700

@royalaid nice. why are you using the node.js JS REPL instead of a CLJS REPL though?

Mostly because I wanted to show what it looks like calling into CLJS from JS

I plan on making a follow up post gluing together DynamoDB and a lambda and using the NodeJS view of the world to show how to two are connected

That being said I also want to show the Dev workflow using the repl to debug too

but it really hard for me to capture that process in a meaningful using just text

It feels like the best way for newcomers to experience the repl is just watching a dev use it, like the first time someone watches a person who knows vim jet around a file

I think it would be less confusing with a CLJS REPL but if showing the interop is your goal I guess thats fine

this way you kinda have to know a few things about the internals

Had the same thought, just finished reading the blog post

Yeah still trying to find my feet with blogging so this feedback helps a ton, thank you!

or this m.aws.createTable() isn't immediately obvious what this actually calls

Now that is something I may make an edit for clarity

shadow-cljs node-repl (require '[server.create-table :as ct]) (ct/invoke) might be cleaner

Someone here knows how to make cljs with live reloading debugabble?

in chrome

which part do you want to debug?

So, in chrome, i am able to set breakpoints in code when i go in Sources tab at js/compiled/out/cljs-runtime/[…] , but when i update the code and live reload it, this code is’nt being updated too

like, i think some implementations put a timestamp on these cljs files url everytime they are updated

why not set the breakpoint in the cljs file?

i set on the cljs,

what i mean is that the files are not being updated as i change them

so i can’t set breakpoints on new code

not sure to be honest. never tried this. the timestamp is mostly used for cache busting, don't think it is used for debugging purposes

it is usefull in the sense that when you cache bust the code you can debug what you have just written without reloading the page again, hah

is it possible to enable it?

you can try to take this file and put it into your classpath

https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/devtools/client/browser.cljs#L63

change that line to add "?rand=" (rand) at the end (after resource-name)

maybe that does the trick

alright

thanks

it might be because shadow-cljs doesn't actually reload files

it loads the files as edn and evals them

so the load isn't async

(and never has cache issues)

if i re-define that function within the namespace it will work too?

sure

i put browser.cljs into the folder path /shadow/cljs/devtools/client but i think it was’t executed again, so i will try that

may need to restart the server for this to work

since it already has the old file loaded and may just ignore the new one

alright

Can you see if this is right? i reloaded the server and i think it did not got this file

assuming src/cljs is your source path?

yea

i tried running the whole file on repl too

on the cljs repl

Hey there, I'm running into trouble getting transitive dependencies to install (in particular the js dependencies of a cljs dependency, macchiato). Anything I'm missing? For now I'm just installing them myself.

@jstaab since most cljs packages still rely on cljsjs and do not support npm they in turn don't properly declare their npm dependencies

so we can't install them automatically

Gotcha

Where would I find the package.json for the installed version of my immediate dependency so I can hack something together?

Or I guess that would be the problem wouldn't it

there is only the package.json in your project which you add the deps to manually

Macchiato has one: https://github.com/macchiato-framework/macchiato-core/blob/master/package.json

Is there any way to get at that? Maybe it's excluded from the installed version

in its project but not in its .jar

where would shadow-cljs put that?

it doesn't exist. do not waste your time looking for it

Ok, thanks

it will be located in the maven repo

so ~/.m2/repository/whatever/macchiato..../something-version.jar

you can check whats in it with jar -tvf that.jar

but even if it would ship its package.json it would not be a common thing to do

so you'd need to talk to every library author to add it

and at that point you could instead convince them to add deps.cljs instead

there is no "standard" for this yet and I don't know what to do to get one

Does shadow-cljs support deps.cljs?

its a complicated situation thats not just solved by adding a package.json or whatever

Sure

:npm-deps in deps.cljs yes. nothing else.

I didn't even realize maven was involved

Ok, cool I'll try that

I mean, it doesn't solve my problem, but seems better than a package.json, which is what I'm currently doing

definitely use a package.json in your project

I cannot emphasize that enough. do NOT rely on deps.cljs

ha

ok

always use package.json and KEEP your lock file

Is deps.cljs just for libs? or is that just the non-existent standard you were talking about?

otherwise npm becomes one unpredicatable mess

yeah, I learned about lockfiles the hard way

deps.cljs is just for libs

ok

thanks again!

This is complex

I started reading shadow's source at one point and got completely lost

it does a lot of stuff these days 😉