This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-01
Channels
- # aws (2)
- # aws-lambda (18)
- # beginners (68)
- # boot (6)
- # cider (2)
- # clara (2)
- # clojars (27)
- # clojure (68)
- # clojure-austin (5)
- # clojure-berlin (6)
- # clojure-dev (28)
- # clojure-greece (7)
- # clojure-italy (46)
- # clojure-japan (3)
- # clojure-nl (1)
- # clojure-russia (8)
- # clojure-sg (1)
- # clojure-spec (17)
- # clojure-uk (86)
- # clojurescript (82)
- # community-development (2)
- # cursive (18)
- # datomic (11)
- # duct (5)
- # fulcro (254)
- # garden (2)
- # graphql (6)
- # hoplon (19)
- # instaparse (4)
- # kekkonen (2)
- # leiningen (4)
- # luminus (3)
- # lumo (9)
- # off-topic (28)
- # om (7)
- # onyx (38)
- # other-languages (27)
- # portkey (7)
- # protorepl (1)
- # re-frame (56)
- # reagent (64)
- # ring (14)
- # ring-swagger (7)
- # shadow-cljs (255)
- # sql (2)
- # vim (11)
- # yada (10)
Hi, it seems I touched nothing but suddenly went into a lot of errors such as
index.js:1 Uncaught TypeError: shadow.js.provide is not a function
at index.js:1
(anonymous) @ index.js:1
emptyObject.js:1 Uncaught TypeError: shadow.js.provide is not a function
at emptyObject.js:1
(anonymous) @ emptyObject.js:1
invariant.js:1 Uncaught TypeError: shadow.js.provide is not a function
at invariant.js:1
Reinstall shadow-cljs
solves this. It may because of I run git pull
in the shadow-cljs
repo. 😕
...
[CACHED] doumi/bottomnav.cljs
-> JS Cache read: 32 JS files
<- JS Cache read: 32 JS files (24 ms)
-> Closure - Optimizing ...
Closure compilation failed with 1 errors
--- EXTERNS:/Users/yuzhao/.m2/repository/cljsjs/d3/4.2.2-0/d3-4.2.2-0.jar!/cljsjs/d3/common/d3.ext.js:670
Object literal contains illegal duplicate key "scaleSequential", disallowed in strict mode
I've already removed d3 from shadow-cljs.edn
and deleted the d3
folder from ~/.m2/repository/cljsjs
, but shadow-cljs
still gives me this error.10774 ± : ls /Users/yuzhao/.m2/repository/cljsjs/d3/ ⏎ [43m] ✹
ls: /Users/yuzhao/.m2/repository/cljsjs/d3/: No such file or directory
===> Hi, I removed the target
folder , removed [braintripping/re-frame-trace "0.1.9"]
and run shadow-cljs release app
again and it works now!
@cmal that error is from an old cljsjs/d3
release, not directly related to shadow-cljs
@thheller I update shadow-cljs
version. And after that I find the old target
prevent me from re-compiling the new code until I removed target
folder when it begins to work.
I can probably add a config option to disable AOT, but then startup will be very slow
OK. Maybe a shadow-cljs clean-aot
to clean the aot. I stared at the [CACHED] things for a while and finally found out removing target
will work. 😄
-> Closure - Optimizing ...
Closure compilation failed with 1 errors
--- EXTERNS:/Users/yuzhao/.m2/repository/cljsjs/d3/4.2.2-0/d3-4.2.2-0.jar!/cljsjs/d3/common/d3.ext.js:670
Object literal contains illegal duplicate key "scaleSequential", disallowed in strict mode
latest version of shadow-re-frame already has that https://github.com/mhuebert/shadow-re-frame/blob/master/shadow-cljs.edn#L8
Never mind. I do not use that any more. But I will write that down, in case later I will use d3
again. 😆
@mhuebert https://clojars.org/braintripping/re-frame-trace still lists the old cljsjs/d3 dependency?
I had removed d3 from the build because that feature doesn’t work anyway, but then was trying to get my fork to be closer to master and forgot about this whole d3 extern fiasco
I didn’t notice because I am not doing an :advanced build for the demo anymore as it causes too many problems with trace
@mhuebert about circleci, if there is something I could add to make integration easier let me know
@thheller I happened to make my attempt last night when circleci itself began having reliability problems
unfortunately i didn’t realize that their platform wasn’t working until later so I gave up on some of the config stuff that might have worked
shadow-cljs happily eats up all the resources it can get since everything is threaded/parallel
it looks like parallelism in circleci means ‘multiple machines’ instead of providing multiple cores or more memory in one machine: https://circleci.com/docs/2.0/parallelism-faster-jobs/
and not sure if it helps us at all. they do give 4 instances for free for open source projects
yuck .. definitely need a “use less resources” option then, parallel builds will actually be slower on one core
which means it is no longer simple to specify an environment that has both nodejs and java
it used to be as simple as specifying a version for both. now, because they only have prebuilt docker images for each individually, you have to make or find your own
I have to confess that I have never used docker … or rather never could get it running.
wait .. circleci is using clojurescript? how do they not have a pre-built image for this
hmm yeah thats enough if you only use cljsjs, guess I need to sell them on shadow-cljs 😉
I cannot get shadow cljs to compile my cljs, I get the error could not find or load main class clojure.main... Google does not give any usefull hints. Going through lein it works , but I don't want to use lein for this project.
pretty sure this is the cause https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/npm/cli.cljs#L33-L34
@eveko try [email protected]
maybe that works
I’m not 100% I handle everything correctly when it comes to windows, I should be in most cases
It is a pity though, I wanted to experiment with some cljs front end, our backend at work is http://asp.net framework on windows
[:app] Compiling ... Nov 01, 2017 8:04:01 PM clojure.tools.logging$eval761$fn__764 invoke WARNING: failed to inspect resource "C:\Users\*\Documents\Visual Studio 2017\Projects\techtest\techtest\src-cljs\main\app.cljs", it will not be available. The required namespace "techtest.app" is not available.
the wsl one also has the same error, but I believe that is because wsl tends to sometimes use the windows binary of noder/yarn
I will try making this work on my home desktop where i can be sure that wsl wont use windows binaries
hmm let me check if it chokes because of the spaces in the file path, eg. Visual Studio 2017
can you try cloning https://github.com/shadow-cljs/quickstart-browser
npm install [email protected]
cause the one I just pulled worked, It also had the visual studio path, so the spaces are not the issue
I got no immediate idea what might be causing your issue. does it dump a full stacktrace?
as the reagent example for some reason doesn’t have a proper require for clojure.string
its a bit unfortunate how reagent is bundled currently, the alpha is a bit in flux and doesn’t properly declare some deps
I “fixed” the watch issue … well it doesn’t error out anymore, but doesn’t update either 😉
now i need to figure out how to make http://asp.net serve the correct path for js
hmm no idea how that works in http://asp.net, never used it
that is for http://asp.net core
but I really don’t know .. the article looks like it should work if configured correctly
@eveko just published [email protected]
which has fixes for all the obvious windows issues I could find