anyways .. wrote it all again in case someone is interested in the vdom stuff. still very far away from something actually usable but some of you seemed interested https://github.com/thheller/shadow-experiments/blob/master/doc/arborist-components.md

Hi, I'm so sorry to bother you. I have run a react-native project, and use a js file in it. The project looks like:

src
├── main
├       ├── main.clj
└── js_libs
├       ├── my.js

Can't find variable: shadow$provide
eval
    [native code]
globalEval
    index.js:828:25
evalLoad
    index.js:2082:24
<unknown>
    index.js:2404:20
loadModuleImplementation
    require.js:331:6
<unknown>
    index.js:1
loadModuleImplementation
    require.js:331:6
guardedLoadModule
    require.js:197:45
global code

@180338742 the JS support currently has issues with commonjs code. try to use ESM import/export instead

Thank you~

Hi all, is it possible to supply a handler-creating fn to :devtools opt?

currently the wiki states :http-handler shadow.http.push-state/handle

but I want to wire my own handler, who is created by invoking a fn (defn make-handler [cfg]...)

in my experience 100% of the time where you need handlers that actually do stuff you should be writing your own server

you are not going to run shadow-cljs in production either

just create your own CLJ server and use that

there is nothing the server needs to do for shadow-cljs to work

Thats great insight; I guess my handler just needs to render the appropriate html file then?

whatever it would be doing in production too yes

just like production the only thing it will need to do is serve static files

(that could be a nginx or something sitting in front of it)

I'm just assuming here that the handler you are talking about is an actual CLJ server-side "app"

thanks @thheller that clears it

@thheller After upgrading shadow and React to the latest version, hot-reloading lazy-loaded components with hx works -- here's an example repo for anyone curious: https://github.com/orestis/shadow-hx-lazy-load

Any clues about what brings in this "@" npm module? It only have date-fns imports.

that it likely datefns

the node_modules/date-fns/package.json is likely empty or doesn't exist at all

or just wasn't read correctly

@ is just because it concats (str package-name "@" version) or something

guess there can be cases where that is empty

Nothing seemingly wrong with node_modules/date-fns/package.json

And there's another date-fns later down the build

dunno might just be a bug not identifying the package correctly

if you can reproduce this feel free to open an issue

The "empty" row is the one of the first screenshot, the expanded date-fns is what I show now.

Cool, I just wanted to see if you had any obvious insights. I'll try to repro.

Interesting: node_modules/date-fns/parseISO/index.js vs node_modules/date-fns/_lib/setUTCDay/index.js -- there's a _lib prefix in the last one.

Hah, it's actually different files. Not sure why the reporting looks off, but the actual content is not duplicated as I thought -- so it's only a reporting glitch.

Hm, shouldn't checking for js/goog.DEBUG result in DCE in release builds?

if you hint it with ^boolean

Ah, I thought that this was fixed in the CLJS compiler? I saw some discussion and "closed" ticket in cljs-dev.

The code I see generated looks like: $APP.l(!1)&&(JO.displayName="nosco.views.page-list/DeletePagesButton")

maybe in master. not in 520

Ah, ok. I'll wait for it to land then.

just hint it

It's in a library 🙂

I got a little bit obsessed with code size, having seen my build balloon to 2MB of JS, so now I'm testing out splitting code etc. Of course, most of it is huge JS libraries.

hehe. yep JS will do that 🙂

Yeah, bringing in their own polyfills even. And then when I wanted to use https://projectfluent.org, they hard-drop IE11 compatibility by extending Map so no polyfill can fix that 😞

If a JS project exports both common.js and ESM versions, like

"main": "dist/react-beautiful-dnd.cjs.js",
  "module": "dist/react-beautiful-dnd.esm.js",

you can try :js-options {:entry-keys ["module" "main"]} to pick module over main

in my experience things break far more often since ESM->CJS interop is still somewhat undefined

Thanks