Is anyone using shadow-cljs with some sort of task runner? I was hoping to use one command to run the build/watch and then run my nodescript outputted by shadow-cljs. I'd normally do this with GulpJS. Are people using tools.deps to do this?

What could be the cause of a situation where shadow-cljs does not complain about a missing ^js but that tag not being present still results in an incorrectly minified name? My guess is that name was used in e.g. Closure library. Are there any other potential causes?

don't know. what kind of form is it?

(set! *warn-on-infer* false) turns everything off, just in case that is in the file?

When setting :compiler-options {:externs ["/app/components/user/payment.js"] i get this:

[:app] Compiling ...
[BABEL] Note: The code generator has deoptimised the styling of /Users/simonchristensen/Documents/Developer/movenation/calculator/node_modules/@firebase/firestore/dist/index.esm2017.js as it exceeds the max of 500KB.
{:type :missing-externs, :extern "/app/components/user/payment.js", :shadow.build.log/level :warn}
{:type :missing-externs, :extern "/app/components/user/payment.js", :shadow.build.log/level :warn}
[:app] Build completed. (3727 files, 3616 compiled, 0 warnings, 95.37s)

fixed by removing / prefix: :compiler-options {:externs ["app/components/user/payment.js"]

But now this file is not supported since, the js version used is too new:

JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT_2015 mode or better: modules. at EXTERNS:app/components/user/payment.js line 1 : 0
JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT_2015 mode or better: modules. at EXTERNS:app/components/user/payment.js line 2 : 0
JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT_2015 mode or better: const declaration. at EXTERNS:app/components/user/payment.js line 5 : 0
JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT_2015 mode or better: object destructuring. at EXTERNS:app/components/user/payment.js line 5 : 6
JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT_2015 mode or better: const declaration. at EXTERNS:app/components/user/payment.js line 6 : 0
JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT_2015 mode or better: const declaration. at EXTERNS:app/components/user/payment.js line 7 : 0
JSC_LANGUAGE_FEATURE. This language feature is only supported for ECMASCRIPT_2015 mode or better: modules. at EXTERNS:app/components/user/payment.js line 9 : 0

what does that mean js version used is too new? there is no point in using new features in externs?

you can't just feed it the normal code? that is not what externs are.

For the :browser-test target, is there any way to influence the path it uses in the index.html file? <script src="/js/test.js"> (I mean the /js/test.js there, I'd like to change that path) I tried setting :asset-path, like one would for the :browser target, but that was ignored.

should be fine? I mean changing it in the html + asset-path?

I've got a library with the :node-library target that has one basic interface point between the clojurescript and javascript worlds. I use a deftype with Object methods to provide the javascript-side interface, e.g.,

(deftype Mediator
  Object
  (opA [this] ...)
  (opB [this in] ...)
  ...)

this really is hard to answer if you take out the part generating inference warnings?

the above snippet should be fine?

@thheller (assuming you are answering me, please disregard if not) Do you mean that the first deftype (without ^js) should not generate inference warnings?

I would add that the inference warnings are still emitted even if I treat the this as a POJO in the methods.

@thheller oh, I thought it would get overwritten constantly. Sounds good.

@genovese you have given only partial of the code and the error message so I do not know what you are talking about. you get an inference warning on what exactly?

what does "deftype ^js Mediator, but that turns the Mediator type into a POJO requiring js-style operations on the object" mean? I do not understand what that means?

do you mean deftype vs defrecord?

deftype with Object methods are completely fine but without knowing more about what exactly you are doing its hard to give a accurate answer

Sorry. First, here's an example of the message:

26 | (deftype Mediator [frame options env]
-------^------------------------------------------------------------------------
 Cannot infer target type in expression (. (. MathLingo -prototype) -render)
--------------------------------------------------------------------------------
  27 |   Object
  28 |   (render [this]
  29 |     (str "TBD" (process frame))))

uhm I'm confused. deftype Mediator but (. MathLingo -prototype)?

Sorry, name changed. Should be (. Mediator -prototype). Not really on my game today 🙂

maybe you are on an old shadow-cljs or clojurescript version?

Hmm...not sure what to make of that. Here's my config

{:source-paths
 ["src/dev"
  "src/main"
  "src/test"]

 :dependencies
 [[better-cond             "2.1.0"]
  [binaryage/oops          "0.7.0"]
  [camel-snake-kebab       "0.4.2"]
  [data.deque              "0.1.0"]
  [instaparse              "1.4.10"]
  [metosin/potpuri         "0.5.3"]
  [com.rpl/specter         "1.1.3"]
  [net.cgrand/xforms       "0.19.2"]
  [org.clojure/algo.monads "0.1.6"]
  [org.clojure/core.match  "1.0.0"]
  [org.clojure/test.check  "1.1.1"]]

 :builds
 {:main {:target :node-library
         :output-to "out/mathlingo.js"
         :exports {:createParser mathlingo.core/create-parser}
         :compiler-options {:infer-externs :auto}
         :devtools {:repl-pprint true}}
  :test {:target    :node-test
         :output-to "out/node-tests.js"
         :ns-regexp "-test$"
         :autorun   false}}

 :nrepl {:port 8777}

 :open-file-command ["emacsclient" "-n" ["+%s:%s" :line :column] :file]}

(deftype Mediator [frame options env]
  Object
  (render [this]
    "TBD"))

this is fine and produces no warnings for me

It does not produce warnings for me at the repl, but when it compiles it does.

I didn't try at the REPL

which version of shadow-cljs? see npx shadow-cljs info

2.6.12 What could I be doing differently? I can try it in a raw project, but I don't see what I can tweak otherwise.

=== Version
jar:            2.16.12
cli:            2.16.12
deps:           1.3.2
config-version: 2.16.12

=== Paths
cli:     /.../node_modules/shadow-cljs/cli/dist.js
config:  /.../shadow-cljs.edn
project: /...
cache:   .shadow-cljs

=== Java
openjdk version "15.0.1" 2020-10-20
OpenJDK Runtime Environment (build 15.0.1+9-18)
OpenJDK 64-Bit Server VM (build 15.0.1+9-18, mixed mode, sharing)

I don't know either. there is nothing to tweak. If you have a reproducible case I'm happy to take a look but so far this all looks fine

OK, thanks. I'll clear the cache and start again. And I'll assume all is ok. I appreciate the help.

you can always turn off inference warnings by (set! *warn-on-infer* false) before the deftype or so and turn it back on again after

I do remember that I had a case where I had to do that myself

but I can't remember any details

Great, that will be more pleasant if it continues.