I just started looking into core.async for clojurescript. Under which conditions would one opt for core.async over js async/await or promises? A use case I am thinking about is a basic http request. Most articles I am reading are written before the mechanisms were part of JS, so I am curious when core.async is the right tool.

Hi there, I've got a reagent/re-frame app in which I get React from cljsjs. Now I want to use a npm package that depends on React and when try to compile I get the error "Error: Can't resolve 'react' in '<PROJEC_HOME>/node_modules/react-select/dist'" Should I also include react as a npm dep?

Is anyone in here running their ClojureScript on ChakraCore (instead of V8)?

On startup, does cljs ignore files that are already compiled, or does it compile everything from scratch each time?

@loganpowell FWIW, ClojureScript’s unit test suite includes ChakraCore.

@mfikes! I saw your YouTube video testing ChakraCore. Thanks for responding. Is it safe for me to replace my Node VM with CC?

I'm running into a v8 limit with JSON.stringify atm 😄

At least as far as ClojureScript’s behavior on ChakraCore, we’ve been (successfully) testing with it for quite a while now.

Is there a specific set of Node and CC versions I should pair together?

FWIW, when ClojureScript is tested with ChakraCore, it is not done with Node-ChackaCore. https://github.com/nodejs/node-chakracore We instead use Microsoft binaries from https://github.com/microsoft/chakracore

Ah, so not ready for Node replacement yet

I wouldn’t conclude that. Node-ChakraCore’s quality likely surrounds how well they integrate the two.

(Even if you ran ClojureScript’s unit tests on Node-ChakraCore, ClojureScript’s unit tests focus on the JavaScript implementation. It never invokes anything that would be in Node.)

Have you tried the node-chakracore setup?

If I have, I don’t recall. 🙂

No worries. If I can't figure out another (potentially hackier) solution, I'll give it a go and let you know

There is also the Node implementation that sits atop Graal.js

Let me check that out

btw, thank you for the apropos channel!

@tkjone The following link might help you. https://groups.google.com/d/msg/clojurescript/LBy0yiZiWrA/vd1TYeD-AwAJ

Has anyone run into an issue with the warning-handlers compiler option as passed in thru project.clj via lein cljsbuild? It looks like with the current version of cljsbuild, the custom warning handler feature always throws an exception: https://github.com/emezeske/lein-cljsbuild/issues/494

Hi ! Is someone familiar with this doc ? https://clojurescript.org/guides/webpack I’m trying to follow “Using Your Foreign Library” with lein and figwheel and I think I understood a lot.. But my browser still displays lot of errors like: goog.require could not find: module$Users$<my_absolute_path_to_my_project>$node_modules$create_react_class$index . I’m trying to include npm modules since yersterday and had so much problems doing it... 😕

Hi! Need help to use js libs! how to? shadow-cljs is worth to look?

@julien.fleury check https://github.com/pesterhazy/presumably/blob/master/posts/double-bundle.md and https://github.com/pesterhazy/double-bundle

Yep, that was one of my first shots, but after testing it, it seems to be outdated 😕

hey everyone. i’m looking for some great projects using cljs / figwheel for node applications to read through and learn from. any recommendations? the larger the better.

@julien.fleury outdated how?

this could be cool https://amphtml.wordpress.com/2018/08/21/workerdom/

Sounds similar to https://github.com/AshleyScirra/via.js

But they essentially queue up actions on the proxied dom object and I don't think it'll work with things that are supposed to return results synchronously.

If you want to retrieve a value from the DOM, it must be accessed asynchronously, since it requires a postMessage round-trip. Via.js provides a global get() function which returns a promise that resolves with the requested DOM property value, e.g.:

I wonder if WorkerDOM has the same limitation

With using SharedArrayBuffers though, and blocking, values retrieved from the dom could be converted back into synchronous operations.

just by waiting on the result

As long as the thing returned by the dom can be serialized

Or maybe not. You could possibly forward your mutation over to the main thread and work on the non-serializable object there. But that sorta defeats the purpose of moving stuff off the main thread.

I don't think it makes much sense in the context of react and such that already batch create dom nodes and can do so async (react v16)

but it could be useful for smaller non-vdom based dom interop

I've heard it can help performance in some situations to move the react renderer into a worker, for the reconciliation crunching

in theory you could do all react ops in a worker and just transfer its patch set over

but in practice thats just annoying to work with 😛

But the blog post you linked said the thing works with react. So maybe you'll get that all for free?

dunno didn't test it yet. it sounds interesting though.

aye

bah. any javascript / react people here?

wondering how to open a new window in the browser, window.open() did not seem to work

window.open is typically blocked by browsers due to ads. you can only open them under specific conditions

basically only on link clicks

hm. i have a data url that I want to open automatically after it has been generated

it's not porn in this case, but yeah I get the issue with that approach

would there be a way to open the window on button click, then pipe the data url to it once it's done?

or do you lose control over the window once it's opened

@restenb you could do it asynchronously using postMessage and window.opener: https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage

i've noticed a lot of cljs code uses native js code instead of their google closure equivalents for stuff like dom/js object manipulation etc. I have noticed the goog versions being slightly slower in some quick benchmarks, but presumably this is due to adding things that are usually justifiable ie browser compatibility. Is there a particular reason for this preference of native js? Is it perception of raw js being "simpler", or closure being unnecessary? non-awareness of the goog stuff? Anything else?

@jjttjj one of the priorities for the closure lib is maximum compatibility

so yeah lots of the stuff in there isn't really that relevant anymore since browser support is a little bit more sane these days (although still not good)

gotcha, makes sense

I guess if you care about old browsers use closure otherwise direct interop is fine

They never updated the UI stuff around the material design and some of it appears old now, like look at the editor: https://google.github.io/closure-library/source/closure/goog/demos/editor/editor.html

more ui examples: https://google.github.io/closure-library/source/closure/goog/demos/

my guess is that those are meant to play well with react, so there are mostly useless for clourescript

or said another way, horrible and painful to use in cljs 😉

But there's lots of great stuff in there not related to the UI

yes, was talking about the UI specifically since that is what you mentioned

It'd be cool to have a version updated with more modern look and feel

material components are being designed to be compatible with closure advanced compile: https://github.com/material-components/material-components-web/blob/master/docs/closure-compiler.md

its sometimes not clear what google does internally. sometimes it feels like half of their own developers never even heard of the closure compiler.

Yeah, I guess it was created by the gmail/maps/docs folks

> At Google, all Javascript is processed and minified by the Closure Compiler

yet some of their open source stuff isn't compatible at all 😛

right

but mdc looks nice on that front. the react binding just aren't that great yet.

that's a shame

anyone know of any reason i wouldn’t be able to require core.async in a .cljc file that defines macros?

i’ve used a reader conditional to pull in the cljs version

I personally have no idea. But I suspect your answer may be found in this direction: https://github.com/cgrand/macrovich

looks interesting. i’ll dig around. thank you

np

Using :foreign-libs and the babel-standalone transformation, I'm compiling alongside from React JSX. This works, but not if there are any import statements within the JSX. Example:

import React from 'react'; // causes goog.require could not find: module$react

export default class Desktop extends React.Component {
  render() { return (<div>"Desktop!"</div>); }
};

bidi leaves the user to handle fragments themselves, right?

cljs.user> (def my-routes ["#/" {"index.html" :index
                           "article.html" :article}])
#'cljs.user/my-routes
cljs.user> (b/path-for my-routes :index)
"#/index.html"
cljs.user> (b/match-route my-routes "#/index.html")
nil