@dnolen @mfikes I think I got it, the node is not a child

(def x x)

@ajchemist: a minimal repro?

Cool!

yeah, obviously that is my typo mistake! but the execption message is quite horror

what the hell 😁

Interestingly, the JavaScript associated with that is simply some.ns.x = some.ns.x. Hmm.

Again, https://github.com/clojure/clojurescript/wiki/Quick-Start led me to this

anyway I’m happy to regain my :advanced optimizations!

@ajchemist: Cool, so while (def x x) is legit in ClojureScript, the fact that it causes an upstream failure with Closure under :advanced is now captured here https://github.com/google/closure-compiler/issues/1899

Hi guys, https://clojure.news is out! HackerNews clone written entirely in Clojure & ClojureScript

Can I prepend the :output-to-file with a custom js-file? I know :preamble exists but I would like something that only prepends to the initial file.

@vikeri: what's the "initial file"?

The output js file, the one that bootstraps the application, loads cljs, goog bootstrap and ultimately my main ns.

^ @martinklepsch

More specifically I want to add a bootstrap script that mocks out some stuff before running tests for React Native. I can accomplish this by running nodemon on this bootstrap file, but it would be neat to use doo directly without nodemon.

is there something like timeago for cljs?

@akiel: You can use goog.i18n.DateTimeFormat and a component that updates in given intervals

@martinklepsch: I use cljs-time now which also has intervals. but it was a bit of work and I have no localization

The intervals were more about triggering re-renders

ah I see - I don’t even have re-rendering

ah ok, so you only want the relative time stuff not the auto-updating (I looked up timeago.js and I thought that's what you wanted 🙂 )

now as you said it, I also want auto-updating 🙂 and everyting in om.next please 🙂

Actually goog.i18n.DateTimeFormat doesn't help but goog.date.relative does: https://github.com/google/closure-library/blob/master/closure/goog/date/relative.js#L25

hmm slack has a problem uploading snippets - so I can’t show what I currently have

but the calculation of the intervals like 5 minutes is easy with cljs-time

so now I only need to figure out how to trigger a re-render in om.next

@bhauman: I'm testing Figwheel repl with Vim-fireplace. Should it support redirecting println output from browser to editor/nrepl?

I guess it should: https://github.com/bhauman/lein-figwheel/blob/9d4d11ed1ad88a5cde9c6186a01d7d08791e446e/sidecar/src/figwheel_sidecar/repl.clj#L56

@juhoteperi: if you are using the latest, then yes, but this is dependent on your apps use of println

Is 0.5.4-7 recent enough? I'm mostly concerned about Fireplace's use of cljs.repl/source which calls println.

https://github.com/bhauman/lein-figwheel/blob/master/support/src/figwheel/client.cljs#L49

hmmm haven't tried that

works for me!!!

lol

so helpful

Could something in the app break the redirection?

just try a standard println

(println 1)

Doesn't work either, it is only printed on the browser console

Works with boot-cljs-repl/weasel

yeah so I would back out the layers until you find the one

vim-fireplace sounds like the new party

but try from lein nrepl

using piggieback of course

Hmm, works from nrepl

@bhauman: Also about Fireplace, do you have opinion about providing cljs-repl-env function which could be used by Fireplace to connect to the repl? Fireplace calls piggieback/cljs-repl so current cljs-repl function doesn't work

(re: https://github.com/tpope/vim-fireplace/pull/222)

can anyone explain how to use (i.e., require) a node module client-side in clojurescript?

e.g., a React component published on NPM

[my guess is that cljs.nodejs won't exist client side and thus nodejs/require won't either]

@juhoteperi: everything you need should be in the figwheel-sidecar.repl ns, if you need a refactoring, or if you want to make a fn available in the repl-api ns I'll take a PR

@bhauman: Impl. here: https://github.com/bhauman/lein-figwheel/compare/master...Deraen:repl-env

hmmm, darn thats going to take some thinking...

please make a PR so that I have a record of it

With some refactoring there wouldn't be need for this much duplication

thats what I mean

but there is a cost for missing something subtle here

Yeah I'm not sure if -repl-options work exactly the same as providing options to piggieback/cljs-repl

etc.

so maybe keeping it separate initialy is better

but I would still like the PR to be able to examine it

anyone?

@johanatan: you're guess is right. You'll need to include the code in some way, built for the browser

@johanatan: normally I compile it with webpack as a UMD module and add it in the :foreign-libs compiler option

@anmonteiro: can you point me to an example on Github?

@johanatan: here’s a Google Groups thread with more information: https://groups.google.com/forum/#!topic/clojurescript/mqQNcT4lHss

@bhauman: PR opened, I'll continue debugging the print redirection problem

@anmonteiro: so I used the re-frame template and it has a lot of stuff setup. I have no idea if it is using CLJSJS React or not (or if that is an important part of that setup).

scanning the 'project.clj' for 'react' and there are none

[i'm guessing that reagent itself pulls in react somehow]

@johanatan: I’m not sure what you’re asking now

is it important that CLJSJS React (rather than some other mechanism of obtaining React) be used?

[the thread you linked to seems to highlight CLJSJS React as crucial to that setup working]

[and if it is important, perhaps I do have CLJSJS React and don't know it (as re-frame/reagent are doing magic beyond what is in project.clj)]

@johanatan: not magic, but Reagent probably pulls React as a transitive dependency

@johanatan: You can check lein deps :tree to check what deps Reagent brings

ahh yep. looks like i do have cljsjs/react

re: thread, I don’t remember the specifics, all I know is it helped me set up a while ago

ok, cool. thx!

@anmonteiro: did you integrate the invocation of webpack from the lein build? or do it as a separate build step coordinated by a GNU makefile or similar ?

@johanatan: in the project I used it in, I did it only once and committed the generated module

ahh, i see

so, looks like this is way overkill for my current purposes anyway as there is CLJSJS module for the component I want to use: https://clojars.org/cljsjs/fixed-data-table

Good to know for future reference though.

Hi, there is a problem with the quick start. The browser repl doesn't work with file urls, so just opening the index.html in the browser won't work, you have to serve the files for it to work, and the tutorial doesn't say so.

On the github clojurescript wiki. It says not to edit it, but to ask here instead 🙂

Here's a related issue https://github.com/cemerick/austin/issues/47

https://github.com/clojure/clojurescript/wiki/Quick-Start

i’m having some trouble making a cljs version of this : http://bl.ocks.org/rkirsling/5001347#index.html

my problem is mainly with the function tick(), it has an updated reference to path which is changed every now and then in restart()

but when i’m using om, i can’t think of a way to make an equivalent tick() where i only initialize force once

and tick always gets the updated reference to path/circle

if i initialize it once in om/IDidMount, it will just tick once and stop

i have to include this: (.on force-layout "tick" (on-tick app)) inside om/IDidUpdate, which makes me feel that i’m doing something wrong

wondering how to add a JSDoc annotation to a protocol function?

should I add it in the implementation or when defining the protocol?