Thin wrapper around Ant Design React components using Reagent https://github.com/hypaer/ant-man

is there a one-liner to start cljs node repl with cli (`clj`)?

Quick question. If I want to translate const { specificComponent } = require('some-library') into ClojureScript, how would that work?

@gekkostate you can try (def SpecificComponent (.-specificComponent (js/require 'some-library')))

what’s a good alternative for println when debugging macros in CLJS node?

@borkdude macros are clojure code so usual tools should apply, when having complex macros I tend to refactor a macro to just call into a clojure function, this function then can be debugged from plain clojure, if you really need printing during a macro call System/out should work

thanks

also macroexpand-1 is your friend (at REPL)

yeah. I have some problem with a macro in a .cljc file which does something depending on an env variable. it’s very finicky to see when it’s called.

the macroexpansion etc is correct, I just want to see why it’s being triggered while it shouldn’t be

I’m undefining some specs in a test, but CLJS spec also does some things at macro-expansion time, so they are undefined in other tests too

I guess I’ll just have to write a different test suite for that one test, since I can’t dynamically switch between defined and undefined

Any recommendations on csv parsers? I’m using https://github.com/testdouble/clojurescript.csv but it’s severely lacking on the read functionality. I was using clojure/data.csv but can’t seem to use it with Clojurescript.

why isn't :parallel-build true the default?

Hello guys

is there anybody experienced any problem with font-awesome icons in clojurescript project?

@joelsanchez historically there were some bugs so wasn't enabled by default

i'm not able to access resources/public/fonts/ content using http calls, actually i proxyed the jar behind nginx

We’re using the public CDN for FontAwesome, but even so, it seems like you ought to be able to access the files in your local resources directories. I assume you’re not having problems with things like resources/public/css and resources/public/js, etc?

Actually, I’m looking at the setup instructions, and it has a webfonts directory instead of just a fonts directory, maybe there’s something misconfigured? https://fontawesome.com/how-to-use/on-the-web/setup/hosting-font-awesome-yourself

@manutter51 so you only refer to CDN urls in your index.html ?

is it working with https or http ? are you using jar directly or as proxy with apache or nginx ?

Actually, what we’re currently using is just one line in the basic index.html page:

<script defer src=""></script>

It’s working fine both in local dev and in our “production” jar, which we have behind nginx

(but of course the fontawesome stuff is coming directly from fontawesome, we’re not getting it through nginx)

in production you are using https ?

it was working fine with me in http mode , when i cconverting to use https i got lost icons

Yeah, if you’re going direct to http://fontawesome.com via https, it should work fine when your app server also goes to https.

Let me double-check if our “prod” server is https

okay sure

btw which is better to use the url like above or download it at js dir and use it like static file ?

ah, ok, no, we’re not behind https yet — I remember now, nginx was so we could put it on port 80

We use the http://fontawesome.com url on the theory that they’ve got more powerful servers than we do.

ah ok

that's really good, thanks 🙂

:thumbsup:

What I want: representation of HTML DOM as CLJS data structures, PLUS a relationship to navigate to/from those data structures and the corresponding DOM object references. Don't really care how I get there, whether starting with hiccup and generating DOM or walking existing DOM and generating hiccup (or whatever). Just for purposes of experimentation. Anybody know of some existing code that does this? Doesn't seem hard, but it's for a side project, and it would be great if this was already done and could save me a little time.

what is the closest cljs thing to java.io.OutputStream? I'm working on porting the [bencode](https://github.com/nrepl/bencode) library to cljs.

Would it be process.stdout?

https://nodejs.org/api/process.html#process_process_stdout

[redacted snippet]

Ok I figured out the immediate issue: When in cljc\cljc you don’t need :require-macros, only in .cljs files. However, that code wouldn’t work or solve the problem anyway since I’m relying on clj->js.

Greetings! I'm trying to use some :npm-deps. However (:require ["some-npm-module" :as xx]) does not work. But on the page served by figwheel required module is available as someNpmModule$$module$Users$myusername$Desktop$myproject$node_modules$some_npm_module$dist$commands. Help :)

Do you also have :install-deps? https://clojurescript.org/reference/compiler-options#npm-deps

yes, :install-deps true

basically, this variable in chrome dev console contains everything module provides, so it is downloaded and visible, but in a funky way

package-lock.json and package.json got generated as well

Does (def xx (js/require "some-npm-module")) work for you @misha?

require is not defined

I used js/require in lein + re-natal setup ~2years ago, and it worked there. Here I am trying to get away with tools.deps + :npm-deps (+ figwheel-main), and understand nothing

@misha are you sure you need to use :npm-deps?

no clue, David, what would be preferred way? Module in question is prosemirror, e.g. but more recent versions: https://github.com/braintripping/re-view/blob/master/prosemirror/src/deps.cljs#L1-L10

if cljsjs would have it – I'd use that.

:npm-deps is an advanced feature, more reliable option is to use https://clojurescript.org/guides/webpack or shadow-cljs

@misha yeah I would avoid :npm-deps and things will get a lot simpler

@dnolen @jayzawrotny it turned out default settings (or I messed it up at some point) of figwheel-main put compiled main.js in project root, and I had some stale main.js in target/public/cljs-out/

Good detective work

it's possible :npm-deps could seem to work - but remember no guarantee advanced compilation will actually work

@rakyi's suggestions are the most reliable ways

so I got page with stale imports, and was chasing my tail. cursive highlighted aliases as unresolved, which did not help either :)

I'll check webpack guide and shadow out, thank you @rakyi @dnolen