@thheller: I put the code in a function that does as shown below (The code can be found here https://github.com/pdenno/nata-borrowed/blob/main/src/nataBorrowed.js) Thanks for the pointer on native encode/decode. There are more functions that I'll need so I'll need to know how to do this anyway. //Top of the file looks like this var utils = require('./utils'); var dateTime = require('./datetime'); const nataBorrowed = (() => { 'use strict'; // Then the function definition // Bottom of file... return { base64encode }; })(); module.exports = nataBorrowed;

Here is a simpler example. Following https://www.sitepoint.com/understanding-module-exports-exports-node-js/, I created const getName = () => { 'use strict'; // Linting wanted this line. return 'Jim'; }; exports.getName = getName; Then I did npm publish --dry-run and copied the results and package.json into a directory that I placed in my program's node_modules directory. It contained: -rw-rw-r-- 1 pdenno pdenno 2009 Nov 17 11:51 package.json -rw-rw-r-- 1 pdenno pdenno 1005 Nov 17 11:55 smallExample-es5.js -rw-rw-r-- 1 pdenno pdenno 829 Nov 17 11:55 smallExample-es5.min.js -rw-rw-r-- 1 pdenno pdenno 0 Nov 17 11:55 smallExample.js -rw-rw-r-- 1 pdenno pdenno 527 Nov 17 11:55 smallExample.min.js I added smallexample 1.0.0 to my program's package.json and fired up shadow. npx shadow-cljs -d nrepl/nrepl:1.0.0 -d cider/piggieback:0.5.3 -d cider/cider-nrepl:0.28.5 watch kaocha-test Connecting with cider-connect-cljs, in the REPL: (se/getName) Execution error (TypeError) at (<cljs repl>:1). module$node_modules$smallexample$smallExample.getName is not a function I suspect that I just don't know how to call the function.

so how do you actually require and call the functions?

and which shadow-cljs version do you use? if you do all this from the REPL there were some issues a while ago

(ns rad-mapper.builtin (:require ... #?(:cljs ["smallexample" :as se]))) Then I'm just calling it with (se/getName) for example. I am using shadow-cljs 2.20.5. It could be something really stupid. This is all pretty new to me.

that would be fine

but there is so much more that could be wrong

like what is your build config? how are you running all this?

why are you making it a npm package in the first place?

To your last two questions: 1. My build config is the :kaocha-test target in this https://github.com/pdenno/RADmapper/blob/main/shadow-cljs.edn 2. I thought that npm would be the natural choice for shadow-cljs, and also the code I'm integrating, from a tool called JSONata, is provided as an npm package. (I have tried loading the entire JSONata npm package, but get the same results.)

so I compiled your project and just added a require for ["jsonata" :as ja] and then added (js/console.log "ja" ja) and it appears to be all fine? I can't test your other package locally? or is it somewhere in that repo?

Well, I think I did warn you that it might be something stupid! My build process created the files shown in the message above, which, as shown, included -rw-rw-r-- 1 pdenno pdenno 0 Nov 17 11:55 smallExample.js which I did not notice is a file of size of 0 bytes. For anyone reading this thread, there were a few useful thing I learned in the process: Most significantly, I didn't realize that, for example, (require '["jsonata" :as ja]) binds ja to the object that you export from the npm module. You can just evaluate ja in the REPL and see the object. The object bound to the empty npm module smallExample.js is #js {}. That's good to know for debugging. Secondly, you might have to explicitly do the require in the REPL. Just being in a namespace that requires it might not be enough. (Or perhaps I have another bug to chase down.) Thanks for the help! Sorry for the noise. shadow-cljs is a great tool.

if you just (in-ns 'your.ns) in the REPL before having loaded it the namespace will indeed be empty and contain no requires

to load it properly you must (require 'your.ns) first

or eval the whole ns form in the REPL

just switching is not enough. common mistake.

Thanks!

Thanks! That works!

where does useLazyLoadQuery come from?

(-> useLazyLoadQuery query) why the ->?

just (useLazyLoadQuery query) should generate the proper code?

it comes from https://www.npmjs.com/package/react-relay

but all depends on what useLazyLoadQuery is

thats not what I meant. where does it come from in your code

is it a :refer or how did you declare it?

the complete component is:

(defnc home []
  (let [{:keys [rates]} (-> useLazyLoadQuery query)]
    (let [{:keys [currency rate]} rates]
      (d/div {:key currency}
             (d/p currency ": " rate)))))
    ;; (d/span {:class "main"}
    ;;  (d/h1 "Welcome to reagent-project")
    ;;  (d/ul
    ;;   (d/li (d/a {:href (path-for :items)} "Items of reagent-project"))
    ;;   (d/li (d/a {:href "/broken/link"} "Broken link"))))
  ;; )

(defn home-page []
  (helix.core/suspense
   {:fallback "loading..."}
   ($ home)))

I need to see the definition of useLazyLoadQuery

sorry

what is that? is it from a :require in your ns? is it a local def?

(ns reagent-project.pages.home
  (:require
   [reagent-project.utils.path-for :refer [path-for]]
   ["react-relay" :refer [useLazyLoadQuery graphql]]
   [helix.core :refer [defnc $]]
   [shadow.cljs.modern :refer [js-template]]
   [helix.dom :as d]
   [reagent.core :as reagent :refer [atom]]))

(def query (js-template graphql "
query reagentProject_pages_homeQuery {
                            rates(currency: \"USD\") {
                              currency
                              rate
                            }
                           }
"))


(defnc home []
  (let [{:keys [rates]} (-> useLazyLoadQuery query)]
    (let [{:keys [currency rate]} rates]
      (d/div {:key currency}
             (d/p currency ": " rate)))))

(defn home-page []
  (helix.core/suspense
   {:fallback "loading..."}
   ($ home)))

ok then remove the ->?

why does it matter though?

I mean the likelyhood of some other compiler recognizing the CLJS output is very slim

ah, I see. I was considering using a vite transform plugin with this. but I think I'll use the babel one instead to complete the transform

so part of the weird code you are seeing is the destructure

(defnc home []
  (let [result (useLazyLoadQuery query)
        {:keys [rates]} result
        {:keys [currency rate]} rates]
    (d/div {:key currency}
      (d/p currency ": " rate))))

might generate code that babel may "accept"

but I wouldn't hold my breath to be honest 😛

nice. thanks again! I'll try that out.

I just release 2.20.12 with the downgraded core.async

In addition the :uberjar profile in project.clj has :aot :all

Thanks, I’ll upgrade shadow-clj