This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-04
Channels
- # boot (41)
- # cljs-dev (1)
- # cljsrn (64)
- # clojure (63)
- # clojure-argentina (2)
- # clojure-austin (1)
- # clojure-russia (1)
- # clojure-spec (1)
- # clojure-uk (59)
- # clojurebridge (1)
- # clojurescript (45)
- # cursive (3)
- # datascript (7)
- # dirac (34)
- # emacs (15)
- # hoplon (1)
- # jobs-discuss (1)
- # jobs-rus (5)
- # klipse (180)
- # lumo (3)
- # om-next (1)
- # re-frame (7)
- # reagent (6)
- # ring (20)
- # specter (10)
- # testing (2)
- # uncomplicate (15)
- # untangled (39)
in boot-reload, when I do
(reload ...
:port
:ws-port
:ws-host
:ip )
my question is: should port/ws-port always be the same and ws-host/ip match up?
If not, what's going on?@qqq one of them is the port the server starts on, and the other is the port the client connects to. They'd only need to be different in some sort of port forwarding scenario. Not something many people need, probably, but I think that's the reason.
Are there any ways to consume npm modules other than https://github.com/degree9/boot-npm ?
need them in both node and browser
@yury.solovyov there are new cljs compiler features in alpha for that, I personally shell out at the moment
@yury.solovyov anything else I can change in boot-npm to make it easier for you to use?
yup, one sec
you commented on the ticket, but I still don't get what should I pass to the task function
(deftask npm-install []
(comp
(npm :package "package.edn")
(target)))
or should I pass map itself?
That should work, might want to use ./package.edn
let me push a branch so I can refer to what I have
here is my edn
and boot task
I meant config
another problem is that it creates additional package.json in target/resources dir
Yeah I think it needs that include option
Iv been doing that on a few of my boot tasks
and generated package.json is still incomplete and does not mirror package.edn
{"name":"boot-npm","version":"0.1.0","dependencies":null}
^ one in the target/resources
That's using the new version?
{"name":"boot-npm","version":"0.1.0","dependencies":{"execa":"^0.5.0","path-to-regexp":"^1.6.0"}}
<- one in just target/
this is with 0.3.0
I even tried deleting target dir
Hmm strange.... not sure where the resources version is coming from
I can do a TeamViewer session if that helps
Cool let's do it
installing TV
Btw
can be used for that too without installing things 😀
Yes I guess it is, I have been using it for a while now
@richiardiandrea good idea!
Woot! new boot-exec
version 0.6.0
fixes the issue mentioned above, boot-npm
will get a dependency update later today with a new version
🎉 boot-npm
version 0.8.0
optional package.json