Clojurians
#lumo
<
2017-01-30
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

stbgz00:01:33

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

stbgz00:01:06

it almost seems to me like the clojars, npm should be treated as implementation details

anmonteiro00:01:45

they're just "repositories"

anmonteiro00:01:50

just like clojars vs maven

stbgz00:01:35

Yeap the responsibility of resolving and loading dependencies appropriately should reside in the build tools irrespective of where they are coming from

dominicm20:01:52

@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.

dominicm20:01:41

Is it possible to require namespaces via relative paths like one does in node?

anmonteiro20:01:56

I don't think I've ever tried it

anmonteiro20:01:13

@dominicm can you open an issue with a failing example that I can try?

anmonteiro20:01:19

don't have time to look into right now

dominicm20:01:03

@anmonteiro sure, no problem.