This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-10
Channels
- # announcements (2)
- # beginners (37)
- # boot (1)
- # cider (76)
- # clara (14)
- # cljs-dev (132)
- # cljsjs (1)
- # cljsrn (2)
- # clojure (18)
- # clojure-colombia (5)
- # clojure-finland (1)
- # clojure-hamburg (1)
- # clojure-italy (2)
- # clojure-nl (8)
- # clojure-russia (1)
- # clojure-spec (28)
- # clojure-uk (85)
- # clojurescript (84)
- # code-reviews (25)
- # cursive (10)
- # data-science (3)
- # datomic (30)
- # editors (1)
- # emacs (3)
- # fulcro (106)
- # graphql (4)
- # hyperfiddle (26)
- # jobs (2)
- # jobs-discuss (124)
- # keechma (3)
- # leiningen (1)
- # lumo (6)
- # off-topic (5)
- # other-lisps (5)
- # reagent (5)
- # ring-swagger (4)
- # shadow-cljs (140)
- # spacemacs (22)
- # specter (2)
- # sql (48)
- # tools-deps (78)
- # vim (7)
not currently functional. use https://shadow-cljs.github.io/docs/UsersGuide.html#target-node-test instead
Can someone point me to a canonical shadow-cljs.edn file (testing and everything included).
if you want to see a gigantic config https://github.com/thheller/shadow-cljs/blob/master/shadow-cljs.edn
but don't take that as a best practice or anything, its my development config with lots of test config builds
the professionals can figure out the details, get the basic structure correct and be aware of cognitive overload
@thheller you mentioned the running nodejs remote fix might be in the next release, just wondering how far that might be?
and should i just check the npm page for updates? or are releases announced elsewhere?
much obliged
I have an app in cljs which compiled within a few dozens of seconds, which is fine. However, now, it takes a very long time, if it ever succeeds. Even after reverting my last changes, compilation seems to take forever. Is there a way to 'debug'/profile compilation? (cross-posted from #clojurescript)
@kurt-o-sys try shadow-cljs watch app --verbose
ok, thx.
the extra warnings from closure you are seeing should be gone in the latest version btw (they didn't matter anyways)
oh, ok, will check.
Am I looking for anything particular in the verbose compilation?
well... it just hangs right now, not sure where exactly:
-> Cache read: ui_app/panels/booking_detail/location.cljs
<- Cache read: ui_app/panels/booking_detail/contact_details.cljs (56 ms)
-> Cache read: ui_app/panels/booking_detail/contact_detail.cljs
<- Cache read: ui_app/panels/booking_detail/location.cljs (19 ms)
<- Cache read: ui_app/panels/booking_detail/contact_detail.cljs (47 ms)
last 5 lines, nothing new apears.
->
means it started doing something, <-
means it finished that something with x time
-> Cache read: cljs/core/match.cljs
doesn't finish
and I found another one.
there may be a few.
ok... let me check.
oh, small... 6.4k
yeah, one of my ns, small one.
will try again
it is. 4.9GB memory, CPU 100%
I haven't got any macro's myself, so it would be another one...
ok...
so, if I add the dependencies to shadow-cljs, it would be easier?
lol, ok 🙂
hi, I’m using a npm library and babel is returning a TypeError
: Uncaught TypeError: Cannot instantiate an arrow function
. Anyone can help me?
@guilherme.teodoro babel is returning?
@thheller nice - that will keep me busy for a while 😛
@kurt-o-sys you can send me the full log to <mailto:[email protected]|[email protected]>. I can take a look if you want
@thheller Thx. I will send
oh, I will try myself first 😛
@kurt-o-sys its very unlikely to be a dependency conflict though. I don't think any dep conflict causes an infinite loop during complation
not sure what it could be though. I've only seen such problems with infinitely expanding macros
@guilherme.teodoro what do you mean by "babel is returning". that looks like a thrown exception in the browser? also the full error would help.
@thheller I seem to be getting there. Probably something with a package called graphql-builder
and queries or syntax or so. At least, I can compile again if I remove some graphql-queries 😛. Thx!
@guilherme.teodoro that @absinthe/socket
package is probably the weirdest code I have ever seen. no idea whats happening though.
@thheller yes, graphql parses plain queries at compile time. The problem seems to be: I defined a query with the same name twice.
@thheller hahaha that’s true.
.bind(void 0)
, getHandlerName = function(e) {
return _newArrowCheck(this, _this$4),
"on" + String(e)
}
.bind(void 0)
, notify = function(e, n, i) {
return _newArrowCheck(this, _this$4),
e.observers.forEach(getNotifier(getHandlerName(n), i))
}
.bind(void 0)
, _this$6 = void 0
, findIndex = function(e, n, i) {
return _newArrowCheck(this, _this$6),
e.findIndex(utilsComposite.hasIn([n], i))
}
.bind(void 0)
, _this$5 = void 0
, remove$1 = function(e) {
return _newArrowCheck(this, _this$5),
function(n) {
return _newArrowCheck(this, _this$5),
utilsArray.remove(findIndex(n, "request", e.request), 1, n)
}
.bind(this)
}
Error:
Uncaught TypeError: Cannot instantiate an arrow function
at exports.default (newArrowCheck.js:8)
at index.js:2
at Object.kitasato$events$create_absinthe_socket [as create_absinthe_socket] (events.cljs:250)
at events.cljs:260
at events.cljs:260
this method:
["@absinthe/socket" :as absinthe]
;; ....
line 250: (.create absinthe phoenix-socket)
@guilherme.teodoro yes I reproduced the error. can't figure out what is happening though. the JS is just weird.
JS made by Elixir developers
I'm lost. can you confirm that this actually works fine in a webpack or so build? I don't see anything shadow-cljs could be doing differently
No, I made the CLJSJS package using the umd version https://unpkg.com/@absinthe/[email protected]/compat/umd/index.js
So, I don’t if works in webpack
you can just require ["@absinthe/socket/compat/umd/index" :as absinthe]
to use that directly
hmmm, I’m gonna try
Same error
When I was using lein, yes
Can I use cljsjs package with shadow-cljs?
just ["@absinthe/socket" :as absinthe]
and calling (absinthe/create nil)
is enough to trigger the problem though
it’s so weird…
https://github.com/thheller/shadow-cljs/issues/365 I'll see if I can figure out when I'm less tired.
Ok, thanks