cherry

wcohen 2023-10-03T19:59:22.202629Z

before i go ahead and push one up, there’s no standardish cherry-compatible logging library that anyone knows of, right? i put a little wrapper around log4js that allows for things like (log/warn "msg") to console etc

borkdude 2023-10-03T20:25:30.829339Z

@wcohen no, cherry doesn't ship with a logging lib, just use one from NPM I'd say

wcohen 2023-10-03T20:25:47.169189Z

thanks!

wcohen 2023-10-03T19:59:52.881669Z

closure library defeated me — i couldn’t get the goog.require to actually load up, in the end

Max 2023-10-03T20:41:09.606349Z

Not surprising, cherry doesn’t have any of the goog namespaces since it doesn’t use the Google Closure Compiler

wcohen 2023-10-03T20:42:25.517759Z

i added google-closure-library as a dep, ignoring the closure compiler, but whatever the library does to get the requires to actually load up the modules is something different — i didn’t realize it needed the compiler, but it does make sense

Max 2023-10-03T20:43:07.993709Z

I don’t know that it does, but I wouldn’t be surprised if it was all entangled somehow

Max 2023-10-03T20:43:53.931339Z

Isn’t console.log/warn/error standard in js? Cherry should have access to that via interop

☝️ 1
wcohen 2023-10-03T20:44:56.256849Z

maybe! i thought it might be helpful to have things like debug and trace — i thought that was a battery that never made it into standard

Max 2023-10-03T20:46:08.621309Z

Seems to be in all browsers and node

wcohen 2023-10-04T01:39:59.788419Z

awesome. thanks. i’m still new to js land compared to jvm