Is there any reason you have to using :simple or :advanced optimizations with Node.js? These settings are primarily for targeting browsers. For quite some time now ClojureScript has supported targeting Node.js with :none.
Perhaps how Closure / Closure Compiler treats `goog.global` is problematic under :simple? Will require someone do more investigation in order to understand what can be done. David On Wed, Dec 10, 2014 at 7:10 AM, Stefano Pugnetti <[email protected]> wrote: > Hi! > > I have to use :simple or :advanced optimization for my code, to be run on > Node.js; now I want to use cljs.core.async timeout channels and I found that > only building with :advanced optimization works; using :simple results in > javascript code that Node.js doesn't like: > > goog.global.setTimeout(a, 0); > ^ > TypeError: Object #<Object> has no method 'setTimeout' > > You can find some exemplifying code at: > > https://github.com/stepugnetti/core.async-issue > > Am I missing something? > > Stefano > > -- > Note that posts from new members are moderated - please be patient with your > first post. > --- > You received this message because you are subscribed to the Google Groups > "ClojureScript" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
