This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-30
Channels
- # bangalore-clj (1)
- # beginners (104)
- # boot (207)
- # cider (173)
- # cljs-dev (157)
- # cljsjs (1)
- # cljsrn (51)
- # clojure (196)
- # clojure-berlin (1)
- # clojure-chicago (1)
- # clojure-italy (4)
- # clojure-new-zealand (1)
- # clojure-nl (1)
- # clojure-russia (28)
- # clojure-spec (17)
- # clojure-uk (73)
- # clojured (13)
- # clojurescript (110)
- # core-async (4)
- # datascript (25)
- # datomic (92)
- # editors (1)
- # emacs (157)
- # events (4)
- # hoplon (16)
- # klipse (74)
- # lein-figwheel (10)
- # leiningen (2)
- # lumo (13)
- # off-topic (78)
- # om (3)
- # om-next (3)
- # onyx (14)
- # protorepl (1)
- # re-frame (17)
- # reagent (23)
- # remote-jobs (1)
- # ring-swagger (33)
- # schema (2)
- # slack-help (3)
- # spacemacs (7)
- # testing (1)
- # yada (7)
one of things I have been thinking about adding to huckleberry/calvin is the ability to deal with dependencies transparently, the clojars npm dualism can be made better through better cljs centric tools
it almost seems to me like the clojars, npm should be treated as implementation details
agreed
they're just "repositories"
just like clojars vs maven
Yeap the responsibility of resolving and loading dependencies appropriately should reside in the build tools irrespective of where they are coming from
@anmonteiro I might be missing something: how do I require namespaces in my code when run via #!/usr/bin/env lumo
? Or is it not possible?
If so, it makes nodejs dependencies hard to use, as the #!
seems to instruct node to look for node modules relative to the symlinked path, not the directory the user is in.
I don't think I've ever tried it
@dominicm can you open an issue with a failing example that I can try?
don't have time to look into right now
@anmonteiro sure, no problem.
thanks!