Clojurians Log v2

using node's net works, I get data printed to stdout from lumo trough the tcp pipe. But I'm haveing diffuculty executeing code that I send via socket.write. As if there's no execute mechanism...

ahh! bingo, delimit with \n was what I was looking for, nice nice nice nice

@anmonteiro any plan on cutting new release?

@honzabrecka hrm I wanted to wait for the next CLJS release but happy to cut a release if you deem necessary

with lumo --help I see -K, --auto-cache Create and use .planck_cache should be .lumo_cache?

😄

PR welcome

nice catch

sooner or later my beer eyes would spot it

lol nice catch 😄

the topic of cutting a new release, I wouldn't protest to that. I tried running lumo on older versions, before the static linkings. Would save me 60mb on my repository not including the binary. But I can wait until next week if cljs will be released.

I can wait too :simple_smile:

@anmonteiro can't build master right now, is that expected?

not expected, what error are you getting?

CI is passing

...
Sifting output files...
Sifting output files...
Sifting output files...
Sifting output files...
Writing target dir(s)...
<...>\lumo\scripts\build.js:83
  );
  ^
SyntaxError: Unexpected token )
...

use Node 8

Node 7 can’t parse trailing commas at the end of function calls

@anmonteiro one down, two more popped up, build failed at second one:

Sifting output files...
Writing target dir(s)...
Building production bundle...
Error: Unexpected key 'pureExternalModules' found, expected one of: acorn, amd, banner, cache, context, dest, entry, exports, external, footer, format, globals, indent, interop, intro, legacy, moduleContext, moduleName, noConflict, onwarn, outro, paths, plugins, preferConst, sourceMap, sourceMapFile, targets, treeshake, useStrict, watch

----> bundle target/bundle.min.js
----> executing browserify via API
events.js:182
      throw er; // Unhandled 'error' event
      ^

Error: Cannot find module 'e:\Workspace\Clojure\lumo\target\bundle.min.js' from 'e:\Workspace\Clojure\lumo'

@moxaj run yarn install

@anmonteiro seems to be working now! Should this be mentioned in the readme? Or was this some special case?

I upgraded stuff recently

@moxaj you’re welcome to add the Node 8 requirement to the readme

@anmonteiro FYI https://github.com/anmonteiro/lumo/compare/master...moxaj:data_readers2

I think this is the approach you hinted at

works in the repl

@moxaj looking good!

i'll do some more testing tomorrow and create the pr

sounds great