Hi, what is the recommended way if any to build something intended for a (node + typescript) consumption? I think the issue is that you need to do :keep-native-requires for node to work, but :keep-native requires leaves as you'd imagine, the requirement as "require" whereas typescript seems to hate that, throwing this error: WARNING in ../node_modules/datahike/datahike.js 112:12-19 vs-sprot-mm: Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

@zhuxun2 no, that is not supported and probably never will be

@zimablue don't know what that error is about, would need to see some code. don't know what :keep-native-requires has to do with anything? when you are using node anyways you absolutely should not be using :js-provider :shadow?

I did not know that I should not be using that js-provider, sorry. In fact that is the one thign I never tried varying

what should I be using?

I pulled the first configuration that I tried from this thread: https://github.com/thheller/shadow-cljs/issues/290

well, I need to know more about what you are building to answer

trying to compile datascript (cljs library) so that it works through an application that uses typescript to target a node runtime

in fact it's datahike, which is a fork

so you use :target :node-library?

yes, although I've tried others in my scattershot attempts

well, it sounds like :node-library would do what you need. if you describe what the problem with that was I can maybe help further

completely basic config, no :js-options config whatsoever

I will strip out all the config and then come back

you recommend to use "release" right, not compile

does infer-externs matter? it is on auto currently

you must use release if you intend to release the actual library to be used in projects. compile or watch will only work on the machine it was compiled on in the directory it was compiled in

matter for what? it only affects the warnings you'll see for your code. nothing else

for working when consumed as a module by typescript I guess

I'll leave as-if and follow your advice

I think I will have already tried that combination, but it will at least give us the relevant error

you don't need to set it at all, auto is the default nowadays (unless you are on a really old version)

I will set it just to let it know I'm serious

it does not affect the code that is generated in any way so I'm unsure what you think it does

sorry, it was a stupid joke

just wanted to be clear that it doesn't affect the generated code 😛 it really only controls whether you see the warnings or not

with the settings that you suggested, the runtime error is this: $environ$core$fs$$.$existsSync$ is not a function. When I look at the code, it's trying to do existsSync on ".lein-env". I'm actually trying to run it in a vscode extension and now wondering whether vscode blocks raw node calls so I'm checking on that also

that looks like you are maybe doing (def fs node-fs) with (:require ["fs" :as node-fs]) or something like that?

oh no ... worse the library is doing that https://github.com/weavejester/environ/blob/master/environ/src/environ/core.cljc#L11

for that you'll need to add manual externs I guess

https://shadow-cljs.github.io/docs/UsersGuide.html#_simplified_externs

or just get rid of that entire library. it doesn't seem to be doing all that much 😛

yes, :require "fs" as fs is happening, both seemingly in that dependency and also in the library main

the problem is when this all gets pushed through a typescript=>node-electron thing though, it all works fine in shadow-cls node-repl

@zimablue the problem is the library uses js/require so externs inference is "hindered" a little. that is why you are seeing the existsSync (and likely the others) getting renamed

so it's expected that it works in node-repl but not when compiled and pushed through typescript?

if that were (:require ["fs" :as fs]) externs inference would be much smarter and generate the proper externs

ah, so it might just be the dependencies having that requirement that's the problem, not the project "main"?

please take a second to understand what externs are

js requires explicit exports, which is not kept without all this being in place

but "manual externs" should work?

they ONLY prevent the renaming of stuff. when you run node-repl NOTHING is getting renamed since it does not run through :advanced compilation

I have taken a second before, it's taken me longer than that definitely xD from memory "variables which should not be renamed"

when you run release things will get named and minified

ah, I see

so with externs you prevent those renames

externs-inference is meant to do this automatically for you but it can only do so when the code is written appropriately. which this library is not. so you need to help it along manually

appropriate is es6 import/export?

or some cljs convention

there is no such thing as es6 import/export in CLJS, but lets please stay on topic here

@zimablue what you need is a externs/your-build-id.txt and just one line for existsSync (and maybe more lines for other stuff getting renamed)

that will make it work fine in release and typescript

normally this should be fixed directly in the code but since it is a library you can't easily do that. unless you are ok with forking it

@zimablue have a look at the Clover extension and see how things are done there. iirc it uses shadow-cljs as the central part of the toolchain. I can also recommend using the #vscode channel for getting some pointers and help from others fighting a similar battle. 😃

I'd honestly just replace that library. Unless you actually want your electron app to be configurable via a .lein-env file?

It's not my personal project to pull libraries out of, I'll follow the explanation you gave, applied to this project and see where I get to

@pez, thanks for that advice I will take a look

@thheller it has been more than a month. I couldn't load my dev-environment in Chromium on Debian Linux and had to resort to working in Firefox without some of the useful tools. The loading of the project was so slow, it basically was just hanging. The issue seems to have been with :devtools {:loader-mode :script} which was there for some (maybe already obsolete) issue. Switching to {:loader-mode :eval} seems to fix the problem. Everything is snappy again

I don't know any details, my colleague found it to fix some of his performance issues and it helped me even more.

Hi, How do I import a react library component in a shadow-cljs / re-frame app? Below isn’t working

//JS version
import { Button } from "@chakra-ui/react";
import { ChakraProvider } from "@chakra-ui/react";

class App extends Component {
  render() {
    return (
      <ChakraProvider>
        <Button
                px="3"
                py="2"
                bg="green.200"
                rounded="md"
                _hover={{ bg: "green.300" }}>
            Click me
        </Button>
        <h1>Hello World</h1>
      </ChakraProvider>
    );
  }
}

//cljs version

(ns todo.views
  (:require
   [re-frame.core :as re-frame]
   [todo.events :as events]
   ["@chakra-ui/react" :refer (ChakraProvider)]
   ["@chakra-ui/react" :refer (Button)]
   [todo.subs :as subs]))

(defn button-panel []
  [:div {:id "button-panel"}
   [:> Button {:px 10 :py 5 :bg "green.200" :on-click
     #(re-frame/dispatch [::events/update-counter 1])} "+"]
   [:> Button {:px 10 :py 5 :bg "green.200" :on-click
     #(re-frame/dispatch [::events/update-counter -1])} "-"]])

(defn main-panel []
  (let [counter (re-frame/subscribe [::subs/counter])]
    [:> ChakraProvider
     [:div
     [:h1 @counter]
     (button-panel)]]))

anyone had any luck getting react-pdf or generally pdfjs working nicely with shadow? feel like I’m mashing a square peg into a round hole, mostly because I’m not super familiar with pdfjs

Hi all: when using :js-provider :external , is it required to have a node_modules installed before compiling with shadow? I'm getting an error without it:

The required namespace "react" is not available, it was required by "reagent/core.cljs".

well the problem there is that reagent.core does (:require [react ...]) as in a symbol

the only way to know that this symbol is referring to an actual npm library it needs to be in node_modules

if that was (:require ["react" ...]) that check is not necessary since we know that strings are reserved for JS libs

currently there is no way to tell it manually that certain symbols should be treated as a npm lib, well besides installing the actual npm lib

I tried advocating for enforcing strings for JS requires but that feedback was ignored so we have this problem unfortunately

Gotcha, the string require does make a lot of sense, it's basically js interop, no sense hiding it. I guess just assuming every missing dependency is externally provided is not feasible?

I suppose not since you still have to check the cljs ones.

It wouldn't make sense to turn it into a warning, would it? "This is missing, better be provided externally" something along those lines?

I won't just make every symbol valid assuming its a npm dependency. there could be typos and stuff

I'd be open to adding a config option to treat certain symbols as npm requires without requiring their presence

maybe I could also just use the :npm-deps from deps.cljs for that

Does shadow-cljs have a tool built in for printing out a graph of namespace requires? I am trying to figure out why cljs.pprint is being included in my production bundle, which I learned using the shadow-cljs.build-report tool.

i don't remember where i heard/read it, but i have a memory that if you use the equivalent of format it will drag pprint in

@dannyfreeman that graph does not currently exist no. requires a bit of manual digging currently to find it. do you use fulcro?

ah nvm thread. yeah expound is one source