This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-01
Channels
- # bangalore-clj (1)
- # beginners (16)
- # bigdata (1)
- # boot (16)
- # cljs-dev (79)
- # cljsjs (37)
- # cljsrn (62)
- # clojars (1)
- # clojure (260)
- # clojure-austin (3)
- # clojure-dev (3)
- # clojure-dusseldorf (3)
- # clojure-italy (1)
- # clojure-russia (32)
- # clojure-serbia (2)
- # clojure-spec (8)
- # clojure-uk (146)
- # clojure-ukraine (16)
- # clojurescript (66)
- # cursive (27)
- # datomic (57)
- # dirac (124)
- # emacs (10)
- # hoplon (12)
- # juxt (6)
- # keechma (6)
- # lein-figwheel (18)
- # leiningen (6)
- # lumo (51)
- # off-topic (1)
- # om (66)
- # onyx (41)
- # perun (1)
- # play-clj (1)
- # protorepl (9)
- # re-frame (20)
- # reagent (11)
- # ring (4)
- # ring-swagger (10)
- # rum (22)
- # specter (8)
- # sql (2)
- # test-check (5)
- # untangled (27)
- # yada (29)
Hi @anmonteiro Any chance of a small release with that change in
@anmonteiro do you know if (
should be able to "read" directories?
@dominicm it won't
but there might be a way 🙂
I mean, you can’t slurp
a resource that represents a directory
@anmonteiro nope, wanted to do an ls
on it
the solution would be lumo.util/fileseq
it’ll return every file in a directory
https://github.com/anmonteiro/lumo/blob/master/src/cljs/bundled/lumo/util.cljs#L190
@anmonteiro but I need to point it at a resource too 😉
@anmonteiro I just noticed Lumo 1.2.0 is not available on Homebrew, is there anything I can do to help get updated there?
@wilkerlucio there’s a problem with building Node 7.5.0 on El Capitan https://github.com/Homebrew/homebrew-core/pull/10169
I’m just waiting for Node 7.7.1 which will be released this week to push a new version /cc @jonpither
@anmonteiro gotcha, thanks for the clarification
what is void?
a Linux package manager?
https://github.com/voidlinux/void-packages/pull/5489 they have packages
@anmonteiro don't suppose you've seen how involved the yarn build process is?
like actually building Yarn?
never looked at it no
@dominicm this looks like it https://github.com/yarnpkg/yarn/blob/master/scripts/build-dist.sh
@dominicm we could also stop requiring Yarn to build Lumo, and just use NPM if Yarn’s not present
https://github.com/yarnpkg/yarn/blob/master/scripts/build-dist.sh#L16 There's something about it being recursive they want to do ^^ using yarn to build yarn
they both do the same thing, I just hopped on the hype train when building Lumo a few months ago
I think yarn is the future™ really. May as well stick with it, not worth the development effort to appease the sense of purity void goes for 😛
Someone will figure out how to get yarn building properly on void really, or they might be happy with what I put together
@dominicm this is really the only place where we use Yarn https://github.com/anmonteiro/lumo/blob/master/build.boot#L57
happy to take a PR changing that to fall back on NPM
not really
oh I see what you’re saying
I suppose I only thought about myself there 🙂
I always add new deps with yarn add …
and that installs it right away
I think it was because I used NPM in the early days
which wasn’t that fast
if you verify it’s fast enough, I don’t mind removing that thing