Fork me on GitHub
#shadow-cljs
<
2022-12-22
>
Joni14:12:52

https://github.com/thheller/shadow-cljs/issues/1071 I updated this issue with a small repo that can reproduce the bug. If you install version 2.19.2 the redirect works as expected, but with the newest version it doesn’t

Hankstenberg16:12:15

Hi guys, I need some help. I'm scratching my head over an error I have with a released bundle. The webapp runs fine in dev mode, but when loading the released bunde statically, it crashes with an "a is null" error. There is no obvious case of "nth" somewhere. --debug doesn't tell me anything. The error even appears if I don't even mount the react stuff. Once I comment that out, basically nothing should happen. I checked all explicit "def"s that could get statically loaded - nothing. Does anybody have an idea what I can do to figure out what's wrong? What I'd need is a version of the compiled code without method/variable "obfuscation". Is that possible?

1
thheller16:12:36

npx shadow-cljs release app --pseudo-names

🙌 1
thheller16:12:50

will be still obfuscated but in a way that lets you figure out what the original was

Hankstenberg16:12:04

I knew there was an arcane option! Thank you very much! 🙂

Klay19:12:46

What’s the difference between the run and clj-run commands?

thheller19:12:24

no difference, same command.

👍 1
borkdude21:12:30

I want to ensure cljs.pprint is only used from a certain module, but stating this in shadow-cljs.edn gives me:

[:main] Build failure:
Module Entry "cljs.pprint" was moved out of module ":scittle.pprint".
It was moved to ":scittle" and used by #{:scittle.pprint :scittle}.
^C%
since shadow itself presumably uses this for dev tooling. It works in the production build though. Any way around this?

thheller05:12:13

in 2.20.16 I just removed the require since it is unused anyways

🙏 1
thheller05:12:34

but yeah its a problem with no fix available currently otherwise