This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-19
Channels
- # beginners (55)
- # boot (1)
- # chestnut (1)
- # cider (130)
- # clara (31)
- # cljsrn (1)
- # clojure (12)
- # clojure-dev (4)
- # clojure-india (1)
- # clojure-italy (2)
- # clojure-uk (33)
- # clojureindia (1)
- # clojurescript (12)
- # component (1)
- # datascript (5)
- # datomic (2)
- # duct (2)
- # emacs (16)
- # hoplon (1)
- # jobs (1)
- # lumo (13)
- # off-topic (3)
- # onyx (4)
- # remote-jobs (1)
- # schema (1)
- # shadow-cljs (110)
- # spacemacs (2)
- # specter (44)
- # vim (6)
jess, 6.0.1
I was sure it was 8 from shadow telling me 😛
I did installed the 8 yesterday, not sure why the one from node -v still 6
I mean node, installed node 8 yesterday
so the latest npm is the problem
but yeah someone reported the 130
a few days ago. no idea where that comes from but it is not happening in v5
I only noticed because I wrapped the shadow calls in npm scripts
then it complains when I stop the compilation
no big deal, just a minor annoyance
sure 🙂
the manifest.edn for content-script is working? I tried using it now, but seems like it's generating multiple files (failing on document_start
)
it always generates multiple files yes. does that not work with document_start
? I tested on idle
and that worked.
no, I got those:
main.js:3016 GET 0 ()
(anonymous) @ main.js:3016
env.load @ main.js:3009
(anonymous) @ main.js:3054
20:57:00.120 main.js:3016 GET 0 ()
(anonymous) @ main.js:3016
env.load @ main.js:3009
(anonymous) @ main.js:3054
20:57:00.120 main.js:3016 GET 0 ()
(anonymous) @ main.js:3016
env.load @ main.js:3009
(anonymous) @ main.js:3054
20:57:00.121 main.js:3016 GET 0 ()
(anonymous) @ main.js:3016
env.load @ main.js:3009
(anonymous) @ main.js:3054
20:57:00.121 main.js:3016 GET 0 ()
(anonymous) @ main.js:3016
env.load @ main.js:3009
(anonymous) @ main.js:3054
20:57:00.140 main.js:3016 GET 0 ()
(anonymous) @ main.js:3016
env.load @ main.js:3009
(anonymous) @ main.js:3054
20:57:00.140 main.js:3016 GET 0 ()
(anonymous) @ main.js:3016
env.load @ main.js:3009
(anonymous) @ main.js:3054
20:57:00.141
I didn't tried using idle
, let me try that just to check if the document_start
is really the problem
I tried, but its even loading now
is this correct?
:content_scripts [{:matches ["<all_urls>"]
:entry fulcro.inspect.chrome.content-script.main
:run_at "document_idle"}]
ok, that's easy at least 😛
I'm on the -
team too
so both work already but it currrently only checks :content-scripts
not :content_scripts
now hte compilation seems fine, but it's failing to connect the repl
is there any other configuration that needs to change?
browser.cljs:310 WebSocket connection to '' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
yes, but I guess it used to work via localhost
I remember it not working by ip
it shows that IP, and it seems correct here: https://www.dropbox.com/s/dlt369wf080csvm/Screenshot%202018-05-18%2021.16.52.png?dl=0
thats a different IP? but the public address is your internet address. thats likely incorrect.
but for some reason seems not connecting, I'm using the company macbook, it might have firewall or something setup (I did the setup long ago, don't remember)
the public ip is for the building here
it's using my local ip
192.168.0.121 refused to connect.
not that I know
0.0.0.0 works too
I tried to force 192.168.0.121 into my /etc/hosts, but that doesn't seem to work either
that was just wrong, no sense 😛
I did disconnected from a VPN during the middle, I'm restarting to try again
restarted server, same thing
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether a4:5e:60:d9:ad:3b
inet 192.168.0.121 netmask 0xffffff00 broadcast 192.168.0.255
media: autoselect
status: active
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
ether 06:5e:60:d9:ad:3b
media: autoselect
status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
ether 1a:77:42:f7:ca:78
inet6 fe80::1877:42ff:fef7:ca78%awdl0 prefixlen 64 scopeid 0x8
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=60<TSO4,TSO6>
ether 6a:00:00:34:ba:00
media: autoselect <full-duplex>
status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=60<TSO4,TSO6>
ether 6a:00:00:34:ba:01
media: autoselect <full-duplex>
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 6a:00:00:34:ba:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x2
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 9 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 10 priority 0 path cost 0
media: <unknown type>
status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::8ea2:2eee:6e4c:561e%utun0 prefixlen 64 scopeid 0xe
nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::d746:7a38:7b:f32%utun1 prefixlen 64 scopeid 0xf
nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::bdc0:d124:6bee:608b%utun2 prefixlen 64 scopeid 0x10
nd6 options=201<PERFORMNUD,DAD>
EHC64: flags=0<> mtu 0
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether 40:6c:8f:55:95:d7
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (none)
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:0a:27:02:00:49:ca:5f
nd6 options=201<PERFORMNUD,DAD>
media: autoselect <full-duplex>
status: inactive
I should just remove all the "smart" logic I added since working on the react-native stuff
hehe, what motivated you to work on figuring the correct ip address?
or rather expo. since I was using my actual phone to test stuff and not an emulator. so localhost didn't work
oh true, would be nice to keep that for RN stuff
and now that you said so, I did RN with shadow, and it worked then
I'll try restarting here
maybe it screws up after a VPN connection
browsers can just use document.location
so its easier there but that breaks for chrome exts
no, still not work
I clicked on the shadow link thinking it was the ip (that was above :P)
issues ready
and :devtools-url
works fine
good night, thanks again, and just to wrap up, document_start
works fine
I’m trying to use Reagent in a node project to render some HTML statically. This is my config:
{:source-paths ["src"]
:dependencies [[reagent "0.8.1"]]
:builds {:app {:target :node-script
:output-to "target/main.js"
:main server.main/main!
:devtools {:after-load server.main/reload!}}}}
This is my require:
(ns server.main
(:require [reagent.dom.server :refer [render-to-static-markup
render-to-string]]))
The error I get:
The required namespace "react" is not available, it was required by "reagent/impl/template.cljs".
although I see react listed in the dependencies of Reagent?How do I get shadow-cljs to output a single .js file that I can use without additional libraries?
e.g. now I get
$ /tmp/html.js
internal/modules/cjs/loader.js:573
throw err;
^
Error: Cannot find module 'react-dom/server'
while it works in the project directory@borkdude node packages are not bundled. since that is not usually how its down for node. typically you'd compile to some directory and put a package.json
there with the dependencies you need
@clojurians.net no there is currently no "recommended" way to abort a reload. why would you want to?
I kept getting this printed to the console when trying to run my tests:
shadow-cljs - config: /Users/kenny/compute_software/clake/cli/shadow-cljs.edn version: 2.3.21
shadow-cljs - starting via "clojure"
[2018-05-19 15:10:33 - WARNING] failed to inspect resource "/Users/kenny/compute_software/clake/cli/test/clake_cli/core_test.cljs", it will not be available.
[:test] Compiling ...
========= Running Tests =======================
Ran 0 tests containing 0 assertions.
0 failures, 0 errors.
===============================================
[:test] Build completed. (26 files, 0 compiled, 0 warnings, 1.98s)
... and could not figure out what was wrong. I had a pretty vanilla test file:
(ns clake-cli.core-test
(:require [cljs.test :refer :all]))
(deftest my-test
(is (= 1 1)))
Turns out I forgot :refer :all
isn't support in CLJS which caused that issue. I suggest make the error message more clear for this case (especially because that is the default file Cursive generates for CLJS tests).