clojurescript 2019-05-17

Edrian Gomez00:05:28

Thanks for your input! I think I’ll do some experiments with scaling different types of apps in both cljs+react and bare react and see what the general trend is like. I’ll report back with any interesting findings

kosengan04:05:12

If anyone is working or having plans on ClojureDart, I would like to get involved! #all-the-channels

Noah Bogart13:05:06

What's clojuredart?

Andy Pai08:05:56

Hi folks, new to this workspace, and to clojurescript. I inherited a reagent project that was using older versions of reagent and clojurescript and I upgraded to current versions. When I try and compile the clojurescript (using figwheel), I get the error java.lang.IllegalArgumentException: /blah/blah/blah.js is not a relative path. Googling around, this error came up and people thought it was an issue with the cljs compiler parsing pathnames incorrectly. Indeed, simply moving the project folder to a different location in the filesystem fixed the problem for multiple developers. Has anyone ever come across this?

Racheal09:05:25

Hey everyone, I keep getting this error: ReferenceError: Can't find variable: ona *** Tests failed! *** TypeError: Attempting to change the setter of an unconfigurable property. TypeError: Attempting to change the setter of an unconfigurable property. when I run lein cljsbuild test and can't seem to solve it for days. I have removed the compiled js test file and recompiled it but seems not to help. I recently upgraded to Ubuntu 18.04.Could that cause the problem? My tests were running fine when I was using Ubuntu 16.04. Any thoughts and suggestions would be appreciated.

dazld14:05:18

hey @mwatelaraycee33 - it might be that your version of node changed

Racheal14:05:35

oohh nice lemme check it out..thanks so much..will give an update

dazld14:05:24

np! looks like v4.x was installed in ubuntu 16.04

dazld14:05:35

could try downgrading and see if that helps

Racheal06:05:45

@dazld unfortunately this did not work

Racheal06:05:26

I downgraded it but it did not work..same to upgrading

dazld10:05:29

i’m sorry then, must be something else! you could try running your stuff in a docker container which corresponds to the old version of ubuntu you had, to see if it’s really upgrading your OS that is causing the problem

Racheal13:05:15

Yeah that's brilliant thanks!

Racheal12:05:44

@dazld i found a solution! i uninstalled phantomjs and re-installed it and it worked!

dazld12:05:29

yay!

dazld12:05:33

congrats!

dazld12:05:42

you know phantom is deprecated though?

dazld12:05:50

try looking into puppeteer instead

Racheal13:05:24

We have actually been moving our project to re-frame and planning to use karma instead

dazld09:05:46

a friend demoed his use of https://www.cypress.io recently, and it was really impressive, might want to check that out too

👍 4

dazld14:05:53

there’s a great script to help with changing versions

dazld14:05:56

https://github.com/tj/n

dazld14:05:14

are there any active channels where people discuss using react native and clojurescript?

mfikes15:05:27

@dazld #cljsrn

❤️ 4

dominicm17:05:00

from reading that load is a repl special form, does that imply I cannot use it in my program the same way I would in clojure to break up a namespace?

mfikes17:05:22

Fundamentally, @dominicm REPL specials only exist in the REPL.

dominicm17:05:39

I thought as much, just wanted to check 🙂

dominicm17:05:13

I wanted to move a bunch of multi-method implementations away from the defmulti, but that's impossible to do without breaking things currently as it would create a circular dependency (or a breaking change)

jsa-aerial21:05:36

Is there a community consensus or opinion on these various JS 'module packaging' things cjs, esm, udm? Or is good ol' straight .js the best approach?

thheller21:05:20

in what context? 🙂

jsa-aerial21:05:46

Well, specifically, I was looking at upgrading the CLJSJS package for cytoscape, but for 3.3+ they only provide esm, cjs, and udm

jsa-aerial21:05:01

I admit to not knowing much of anything about this stuff

thheller21:05:35

well in the case of CLJSJS you don't really have a choice and can't use esm or cjs

thheller21:05:49

so only umd will work (ie. the thing that exports a global variable)

jsa-aerial21:05:28

Ah, is that because 'umd' is universal and works in the 'old' way as well?

thheller21:05:14

yes it typically has 3 "branches". one for commonjs require, one for AMD-style require.js and one that just exports a global (ie. works as a <script> tag)

jsa-aerial21:05:42

OK, that makes sense, so the exported global is what is needed in this context (for externs)?

thheller21:05:43

it is the var that the CLJS code will access (and externs prevent the renaming yes)

✔️ 4

2019-05-17

Channels