In clojurescript you have to require macros separately using :require-macros in the ns form https://clojurescript.org/guides/ns-forms#_macros

You're using :require-macros in util ns but not in the parse ns. My guess is you just need to tweak that to use your slurp macro

Hmmm, since I am using :require-macros from util.cljc, things should be good, right? It's equivalent to, util.cljs:

(ns parse
  (:require [util :refer [slurp]]))

(comment
  (slurp "shadow-cljs.edn"))

(ns util
  (:refer-clojure :exclude [slurp]))

(defmacro slurp [file]
  (clojure.core/slurp file))

might be a bug. does (require 'parse) (parse/slurp ...) work?

maybe you want to use this instead? https://clojureverse.org/t/using-none-code-resources-in-cljs-builds/3745

I'll try the shadow.resource way. Doesn't matter much for my current use case, but seems like something that I should be using generally.

As for the macro problem. It is quite strange. I get different results with require, but it doesn't quite work as I expect.

cljs.user=> shadow-cljs - #4 ready!
(require 'parse) 
nil
cljs.user=> (parse/slurp "shadow-cljs.edn")
------ WARNING - :undeclared-var -----------------------------------------------
 Resource: <eval>:1:2
 Use of undeclared Var parse/slurp
--------------------------------------------------------------------------------

cljs.user=> (in-ns 'parse)
nil
parse=> (parse/slurp "shadow-cljs.edn")
------ WARNING - :undeclared-var -----------------------------------------------
 Resource: <eval>:1:2
 Use of undeclared Var parse/slurp
--------------------------------------------------------------------------------

parse=> (slurp "shadow-cljs.edn")
";; shadow-cljs configuration\n{:source-paths\n [\"src/dev\"\n  \"src/main\"\n  \"src/test\"]\n\n :dependencies\n []\n\n :builds\n {}}\n"

And trying with both qualified and non-qualified with load-file:

cljs.user=> shadow-cljs - #4 ready!
(load-file "src/main/parse.cljs")
[]
cljs.user=> (parse/slurp "shadow-cljs.edn")
------ WARNING - :undeclared-var -----------------------------------------------
 Resource: <eval>:1:2
 Use of undeclared Var parse/slurp
--------------------------------------------------------------------------------

cljs.user=> (in-ns 'parse)
nil
parse=> (parse/slurp "shadow-cljs.edn")
------ WARNING - :undeclared-var -----------------------------------------------
 Resource: <eval>:1:2
 Use of undeclared Var parse/slurp
--------------------------------------------------------------------------------

parse=> (slurp "shadow-cljs.edn")

Execution error (TypeError) at (<cljs repl>:1).
Cannot read properties of undefined (reading 'call')
:repl/exception!
parse=> (load-file "src/main/parse.cljs")
[]
parse=> (slurp "shadow-cljs.edn")
";; shadow-cljs configuration\n{:source-paths\n [\"src/dev\"\n  \"src/main\"\n  \"src/test\"]\n\n :dependencies\n []\n\n :builds\n {}}\n"

could be that the REPL just forgets to load the macros

too tired to check now. feel free to open an issue, so I don't forget to check

👍

When writing the issue and trying to minimize it further, I notice that my repro with require was crap. It does work with require, it is with load-file it doesn't work. I also found out another interesting detail <- click-bait https://github.com/thheller/shadow-cljs/issues/1059

Currently only :target :esm adds the proper code to make that work

maybe you can use :target :esm instead?

I guess you can also sort of make it work by adding :prepend "global.shadow_esm_import = function(s) { return import(s); };" to your build config

I tried it, but I would have to change a quite a few things since it is a big project and I'm doing non-standard things. Many errors.

I'll try your suggestion

That worked. I added it to :target-defaults :node-library :prepend . Thank you for your help.

so it can't find the digest ns. This is a CLJ error, it is not from shadow-cljs. So I'm guessing you maybe don't have a deps.edn alias activated or something like that

also note that :js-provider :import will cause shadow-cljs to not bundle any npm dependencies. so your build report will shrink, depending on how many you used. it'll only contain cljs code after that. don't get mislead by that. the build will only work if something else provides those dependencies, so be sure to compare the final size. not the build reports.

Thanks, I'll look into the alias stuff. Our aliases haven't changed recently so I wonder if there was an underlying CLJ change that is now incompatible with our current setup Also appreciate the tip with :js-provider :import - that makes sense

have you enabled this?