This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-04
Channels
- # architecture (20)
- # aws (8)
- # beginners (13)
- # boot (9)
- # cider (80)
- # cljs-dev (69)
- # cljsrn (7)
- # clojure (243)
- # clojure-dusseldorf (8)
- # clojure-italy (5)
- # clojure-norway (3)
- # clojure-poland (57)
- # clojure-russia (10)
- # clojure-shanghai (2)
- # clojure-spec (11)
- # clojure-uk (50)
- # clojurescript (198)
- # core-async (11)
- # crypto (2)
- # cursive (14)
- # datomic (17)
- # figwheel (8)
- # garden (7)
- # hoplon (8)
- # incanter (4)
- # jobs (1)
- # leiningen (1)
- # liberator (38)
- # lumo (28)
- # om (55)
- # onyx (10)
- # pedestal (13)
- # perun (20)
- # re-frame (1)
- # reagent (16)
- # ring-swagger (9)
- # spacemacs (11)
- # test-check (9)
- # unrepl (43)
- # untangled (163)
- # yada (8)
Probably a bad idea to build the non releases but it fails
SyntaxError: /home/hlolli/lumo/src/js/repl.js: Unexpected token, expected ) (301:15)
@hlolli shouldn’t fail
how are you building it?
weird, did you run yarn
?
I update dependencies now and then
next thing to try is upgrading your Node version maybe
all I can tell you is CI can build it, and so can I
Yarn did updated some deps, so five it few mintutes in the compilation and I can confirm it works...
now it stops here
WARN: Dropping unused variable exports [target/jszip.js:1,350]
/home/hlolli/lumo/node_modules/nexe/lib/exe.js:628
const = Array.isArray(patchFns) ? patchFns : [patchFns]
^
SyntaxError: Unexpected token =
at createScript (vm.js:53:10)
at Object.runInThisContext (vm.js:95:10)
at Module._compile (module.js:543:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (/home/hlolli/lumo/node_modules/nexe/lib/index.js:1:80)
hmmm, only difference from my last compilation of lumo is actually that I updated from Node7.0 to Node7.8. But there's nothing wrong with lumo as of last successful compilation.@hlolli yes, that’s expected now
working on fixing it right now!
dumb yarn registry doesn’t know my latest commit
@hlolli pull again, and make sure to run:
rm -rf node_modules
yarn cache clean
yarn
@hlolli just built Lumo with current master and it worked again
waiting on CI to confirm it
also Lumo should be faster to startup on current master than 1.2.0 and 1.3.0 🎉
there was a little perf regression caused by the inclusion of Google Closure Compiler JS
still not as fast as the first releases though. I bet I can make it a little faster 🙂
@hlolli are you looking to solve https://github.com/anmonteiro/lumo/issues/104 ?
happy to guide you through it if you are!