Fork me on GitHub
#cljsrn
<
2020-05-26
>
pez06:05:07

@olivergeorge, thanks, that got me a bit further. Now I got an error about the file not being found, which also gave me some hint about where it looked for the file. However, fixing the path and making a new clean build brings me back to where no image is rendered and no error messages anywhere. Truly odd.

pez06:05:58

@thheller with shadow-cljs I get back something that I imagine is a file descriptor when I evaluate the js/require at the REPL: Same with Figwheel.

thheller06:05:54

@pez that is only true if the require was part of the initially loaded code. if you require something "new" from the REPL then it will be missing.

👍 4
dnolen12:05:31

@pez you can debug the assets things pretty easily by looking at :output-dir/krell_assets.js

dnolen12:05:43

either the paths are right or they're wrong - that's the only reason they wouldn't show up

pez14:05:00

@dnolen that file looks fine afaict. Is there a Krell log file I can look at, similar to the figwheel server log?

dnolen15:05:57

@pez the paths in that file should be relative paths to where your images are

dnolen15:05:55

actually I guess those will be absolute? point is they have to be something that Metro can find

pez15:05:35

The path is relative to to the krell_assets.js file itself. I’m not allowed to use absolute paths in the js/require.

pez15:05:33

I’ll see if I can repro it in a public repo.

dnolen15:05:58

that would help a lot - I haven't heard of anyone else having problems with assets - what platform? Linux / OS X?

pez15:05:17

OS X. I’m thinking I am probably doing something wrong, but can’t see what myself. Public repro coming up later today. 😃

pez23:05:18

@dnolen Of course it works in the new project... Which is here, fwiw. https://github.com/PEZ/awesome-krell-project The only difference from my other project is the project name, afaict. Some cache somewhere, like @olivergeorge suggested, maybe.