Clojurians
#lumo
<
2017-11-08
>

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

richiardiandrea00:11:08

@dominicm it is just a simple require, but you have to setup the module's package.json (`macrovich` in this case) in order for lumo to find your namespaces, more details here https://github.com/anmonteiro/lumo/issues/130

hlolli10:11:14

I wonder if we should hold out a database of lumo packages hosted on npm...

dominicm10:11:36

Could we tag them?

dominicm10:11:42

and then do it that way

dominicm10:11:50

that's how other npm packages work

hlolli11:11:11

You mean keywords? Another idea would be prefixes like gulp-insertnamehere, but lumo-insertnamehere. Don't know, I just worry that packages that can save me the time to write interop functions won't be found.

dominicm12:11:41

keywords probably sounds right

hlolli12:11:00

I'd like to see someone make lumo-express and lumo-electron, throwing ideas out there :slightly_smiling_face:

souenzzo15:11:05

all packages on npm are lumo package... as lumo runs on node...

hlolli16:11:44

yes, I'd always welcome writing my code (function arg) instead of (.method (js/require "package") arg), and more example where the interop can be abstracted to clojure records/methods and simple functions. But I get your point.

richiardiandrea19:11:32

that's a good point actually, there is a distinction between cljs lumo packages and javascript lumo packages at the moment

richiardiandrea19:11:30

the former will contain only clj/cljs/cljc files...and it can be required with normal (ns myns.core (:require [...]))

richiardiandrea19:11:34

the latter (the whole npm minus one package - macrovich) can be required with eithr js/require (old way) and (:require [bunyan[) (new way) and contains JS code

richiardiandrea20:11:17

for JS consumption, we could compile packages down in a package.json script: {"prepare"} step