This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-04-11
Channels
- # announcements (2)
- # babashka (31)
- # beginners (31)
- # calva (30)
- # cider (23)
- # clerk (1)
- # clojure (46)
- # clojure-austin (5)
- # clojure-brasil (1)
- # clojure-europe (47)
- # clojure-nl (1)
- # clojure-norway (72)
- # clojure-uk (2)
- # clojurescript (39)
- # conjure (1)
- # cursive (16)
- # data-science (1)
- # datomic (35)
- # dev-tooling (4)
- # events (5)
- # introduce-yourself (2)
- # jobs-discuss (5)
- # missionary (3)
- # polylith (11)
- # releases (4)
- # scittle (4)
- # shadow-cljs (18)
- # spacemacs (16)
- # specter (2)
- # squint (27)
- # xtdb (6)
does shadow-cljs still run things through gcc even with :js-provider :shadow
? I seem to get gcc chokin on one of the npm dependencies with IllegalStateException: Expected a property access or array pattern: OBJECT_PATTERN
and I'm trying to figure how to get around that. Is something like this https://code.thheller.com/blog/shadow-cljs/2020/05/08/how-about-webpack-now.html what I have to do for now?
unfortunately the number of packages that don't work keeps growing, so I may have to change that at some point
:js-provider :external
is the "simplest" transition if you must use packages that are breaking
it's the duckdb-wasm that's breaking, not a trivial dependency to replace unfortunately 🙂
that's fair
I think :external
did the trick for me, though, so I'll use that in the meantime
I would never consider such a package for anything frontend? how do you justify a 30mb+ wasm file? 😛
datascript chokes and dies on my input json 🙂
like, I'd really prefer to use datascript, but I can't even ingest the data I have, and duckdb can (I'm writing an irc log viewer/grep tool here for a hobby project and I basically have a 100mb long json)
:thinking_face:
I don't think service workers get more than 4g ram either
no matter what you use loading a 100mb json file will probably lock your entire UI for seconds if you don't do it in a worker
ah. well, it's not a problem because it's not that it loads long. it's that datascript ooms.
duckdb doesn't have to load the whole file, though, so much lower memory requirements (with a feasible speed tradeoff)