Clojurians Log v2

IIRC, http://shadow-cljs.org used to have a homepage. It is now linked back to the GitHub repo instead, is it intentional? Also, is the latest docs still the User Guide Version 1.0 dated Jan 10, 2018? Thanks!

I never bother to update the date on the docs. doesn't mean anything anyways. it is still current. The homepage I'll restore when I have time, not high prio right now

Excellent to know. The GitHub repo is indeed very resourceful and full of helpful information already. Many thanks for creating and maintaining such a fantastic and important tool.

Hi all, I'm having some difficulty with dynamic module loading. The error returned by the loader doesn't give much info, but pasting the generated js into the console gives me the following. Anybody know how to fix this?

@isak

Hi. I loaded a react native npm package and its peer dependencies into my project. They are present in my package.json file and my require is correct, but

[:> ls/LoginScreen]
returns
[:> nil]

@hadilsabbagh18 what is ls? what is your require? read the section about :default, maybe thats it https://shadow-cljs.github.io/docs/UsersGuide.html#_using_npm_packages

could be related to how you are loading the files. pasting code into the console is not something you should be doing

Not a familiar issue then huh? Yeah the pasting was a last attempt to get some useful error info (maybe it's misleading though?), the actual error returned by the loader just says... 1.

it could be polyfill problems. try deleting .shadow-cljs/builds/<build-id>/dev and rebuild

but diagnosing things by loading it in the console is making things harder not easier

the loader you can easily skip by just making a HTML file and putting script tags after each other for all the files it is supposed to load

in the correct order of course

but no need to use the loader

@thheller Sorry

(require '["react-native-login-screen" :as le])

I don't know the package but it might be :default LoginScreen

Ok let me try that.

That works! Thanks a lot @thheller!!!

It's only happening in a prod environment unfortunately, so deleting the build files probably won't help... though it may be worth looking into whether those are cleared on the server before each build. Copying into a script tag is probably worth trying too, but putting the code into the original html file won't work, since it's not a dev environment. Anyway, thanks for the help, I'll continue to play around with it.

Thanks for the help @thheller, your suggestion of clearing the .shadow-cljs let me repro the issue locally, turned out to be a bug in an outdated version of shadow-cljs.