This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-16
Channels
- # beginners (7)
- # boot (63)
- # capetown (1)
- # cider (20)
- # clara (15)
- # cljs-dev (5)
- # clojure (195)
- # clojure-austria (2)
- # clojure-dev (46)
- # clojure-dusseldorf (9)
- # clojure-germany (6)
- # clojure-greece (36)
- # clojure-italy (5)
- # clojure-nl (4)
- # clojure-russia (173)
- # clojure-sg (1)
- # clojure-spec (93)
- # clojure-uk (65)
- # clojure-ukraine (2)
- # clojured (9)
- # clojureremote (1)
- # clojurescript (52)
- # core-async (14)
- # core-logic (5)
- # cursive (21)
- # data-science (8)
- # datomic (60)
- # emacs (83)
- # jobs (9)
- # jobs-discuss (7)
- # juxt (6)
- # klipse (2)
- # leiningen (1)
- # lumo (24)
- # mount (4)
- # numerical-computing (1)
- # off-topic (18)
- # om (37)
- # om-next (5)
- # onyx (13)
- # pedestal (1)
- # perun (44)
- # proton (2)
- # rdf (3)
- # re-frame (24)
- # reagent (4)
- # remote-jobs (3)
- # spacemacs (3)
- # testing (6)
- # vim (10)
- # yada (2)
hey @npeckman I committed a change that could serve as an example for jzip take a look at https://github.com/eginez/calvin/blob/cljs-build/src/main/clojure/eginez/calvin/cljs_deps.cljc#L55
the ZipFile
type is implemented here https://github.com/eginez/calvin/blob/cljs-build/src/main/clojure/eginez/calvin/io.cljs#L15
and I am actually not using the latest version of jzip but the 2.x version that has more sync type functions (2.6.1 to be precise)
A year ago, I tried rallying some support for a standardized cljs config file, but I got some pushback on using it for dependencies
the arguments made sense in the jvm ecosystem where lein and boot had their own
i think calvin is a neat bridge to re-use current jvm standards, but ultimately I think we’re a bit overdue on clojurescript having an official package.json-like config file, now that the lumo dependency story is trying to form (as planck’s was last year)
boot-cljs already supports .cljs.edn files, doesn't it?
Wouldn't that format work?
not quite-- boot-cljs .cljs.edn files hold a config for a single build, and must be in the same directory as the compiler output-dir
the boot-cljs developers may want to collaborate though
@shaunlebron I actually support re-thinking how to specify dependencies and configurations, some of the concepts that we have been carrying around just don’t make sense in cljs,(for example classpath). One of the things I’d like to improve on is the mix clojars/npm dependencies, whatever standard we agree on should try to abstract the concept of where the dependencies are coming from
that’s really interesting
@anmonteiro is there any reader conditional for lumo? It would be nice to specify that the file system stuff in lumo works in a particular way.
not really, not yet at least
this may help https://github.com/cgrand/macrovich
@anmonteiro we were looking for something like: #?(:lumo/cljs (fs.readSync) :clj (io/file) :cljs nil) So not quite. For now, aero is lumo cljs only.
@dominicm yeah I know exactly what you need
me and Mike Fikes have started thinking about ways to solve that problem
^ this is the GitHub org where we’ll eventually continue our work