hmm that's strange, I removed :npm-deps from the compiler options and the problem is still here... maybe this is a compiler cache issue

well this is strange... I nuked the target directory entirely and the problem is still here

so much state 😭

what on earth... I removed node_modules too and it's still happening

Now I'm getting ReferenceError: $jscomp is not defined

this is so brittle...

now every time I build I get Unable to resolve symbol: import in this context 1993 without a filename

finally got everything to work by completely busting the cache and removing node_modules, but now every time I add it back I get the same error... it seems figwheel+reagent+react-dom really don't work well together at all, which is kind of baffling to me

I’d take it to #figwheel or #figwheel-main , then 🙂 And alternatively, you could try using shadow-cljs, it seems to be pretty good for npm deps. I believe npm deps are newer to figwheel than to shadow-cljs, but I also think that Bruce is pretty active and motivated in fixing whatever npm deps problem you might be having with figwheel.

clojurescript exports to unreadable javascript code so I don't think you can use it for a gist

but I'm also a beginner maybe someone else can give you a better answer

If you don’t use any optimization, you can see the correlation if you squint a bit, but it won’t really be useful. Why do you want a gist of the generated code?

Not necessarily a gist. Just a js file that I can load via <script>. It's for a roamresearch extension

If your CLJS snippets don't require any dependencies, then you can use http://app.klipse.tech/

They do :/

Ah, then I'd just follow the shadow-cljs user's guide. :) You should end up with a scaffolding that has just 2-3 files with a few lines in them.

if you're doing backend development, why not go straight for clojure instead of clojurescript? If you're still using clojurescript for backend (for whatever reason), maybe try using what you're already used to in JS but interop with it in CLJS, should get you up and running quickly

It's a backend for my web crawler. I plan to use puppeteer js for the scraping part because puppeteer doesn't have a java client, now I just need a way to persist the scraped data. In Node land I use typeorm for this kind of stuff buts its tied heavily to typescript, guess I will try to find a light alternative (something more like next.jdbc for node). Thank you!

There's Etaoin to remote-control browsers from Clojure, I'm using it in production here for a web crawler/scraper.

Wow I didn't know about it. Thank you! May I ask have you used Puppeteer before, and if so is there any major difference between the two?

I've used both, for scraping as well 🙂 Etaoin is nice in that it's still using webdriver protocol, so easier to integrate everywhere. Mostly it's just the API itself that differ, as Etaoin is made in traditional clojure fashion (works well with repl workflow) while puppeteer as a traditional JS API (wants to evaluate and rerun the entire file on change). Of course this can be worked around, but no need when a nice API already exists. When using Etaoin for testing I also managed to get all of Chrome, Firefox and Safari to work it and I think puppeteer only works with chrome and firefox (3rd party)

(although, haven't used puppeteer from clojurescript, only vanilla js)

This is super useful, thank you guys.

I would write the simplest implementation that comes to mind, measure its performance, and tweak it till it's sufficient. Hard to say anything in advance, especially without knowing the target PCs' specs and the function.

^. My backup plan would be a plain javascript array with length 500*500, then just calculate the index based on x and y.

Thanks for the advice! I like the simple sound of a plain 1d javascript array. Reminds me of https://github.com/mikera/imagez, which uses a 1d java array to store images. That was a pleasure to work with.

What kind of functions are you appointing over the data? There are various WebGL backed matrix implementations for JavaScript, even if you’re not using WebGL for rendering.

Plain math, at least to begin with. Coordinate transformations, colors

Ah never mind, it's not a problem with implementation, it's just CORS authentication. Doesn't even matter for the final web app.

According to that example, row is a function that has to return an element. By itself, row is not a component. Try replacing [row] with just row and wrapping the whole body of the row function in (reagent.core/as-element ...).

thanks @U2FRKM4TW, I did as suggested + switch to material ui, it works but style seems not to work properly,

(defn row [index style]
  (r/as-element
   [:> ListItem {:button true
                 :style style
                 :key index}
    [:> ListItemText {:primary "test"}]]))

(defn example []
  [:> FixedSizeList {:height 500
                     :item-count 200
                     :item-size 200
                     :width 300
                     :border "1px solid black"}
   row])

(defn iam-app []
  [:<>
   [:div [example]]])

renderRow.propTypes = {
  index: PropTypes.number.isRequired,
  style: PropTypes.object.isRequired,
};

all good, I need to destructure the params passed to row properly, thanks