lumo 2019-04-10

@hlolli heads up I’m making a Lumo release today

if you wanna package it up for Nix 🙂

@anmonteiro wish I had a macos to fix the problem you were having as well.

I can’t remember what it was

but to set expectations: I don’t plan on finding out or fixing 😛

this release was already very painful as it is

ok, excited to see if this brings any challenges

should be straightforward

the build process is exactly the same

was painful because I chose to upgrade to the latest Node (11.13)

and let me tell you…

🙂 1

are the experimental threads now non-experimental in 11x?

@danie has joined the channel

@mike.myers has joined the channel

Hi all, I'm trying to get lumo working with transit-cljs, which depends on transit-js. I can't solve it, it keeps on failing when I run it with: Error: Undefined nameToPath for com.cognitect.transit I tried: - Listing the two jars as --dependencies - Listing the two jars as --classpath - Unpacking the jars and including them in (b/build) The Makefile here shows what I've tried: https://github.com/danieroux/lumo-poc/blob/master/Makefile Can someone help me to get this running?

lumo --classpath src:libs/com/cognitect/transit-js/0.8.846/transit-js-0.8.846.jar:libs/com/cognitect/transit-cljs/0.8.256/transit-cljs-0.8.256.jar build.cljs
looks about right (with quotes in the bash ofc) did you try requireing cognitect.transit-js in the root, so that it's defenitely included in the final js. But this looks like a bug to me. @danie

transit.js says goog.provide("com.cognitect.transit"), so something like this?

(ns tech.matterindustries.titan.gateway.core
  (:require [fs]
            [cognitect.transit :as t]
            [com.cognitect.transit]))
I still have the same problem then.

transit should already be included inside the lumo binary though

lumo --classpath src build.cljs with the same requires gets me the same error message 😕

I wonder if that’s part of the problem

yeah it could be a bug

I’m not gonna look into it any time soon, but feel free to open an issue