looks fine. there is no difference in how these are looked up, so no clue what would cause this

except maybe that the trace is brian/client.cljs. yet you pasted a snippet with a reader conditional, which are only valid in .cljc files?

maybe there is an extra client.cljc somewhere that only included by another deps.edn alias?

arg .. nevermind. got confused by my own trace logic 😛

text field is cljc

yeah dunno

could it be source-paths vs deps.edn path?

:source-paths in shadow-cljs.edn have no effect if deps.edn is used

in my shadow-cljs.edn I have:

{:deps     {:aliases [:dev :rad-dev]}...}

yep, then :source-paths or :dependencies have zero effect and are not used when using the shadow-cljs command

but since that specifies other aliases I suspect there is just a difference in those aliases and the paths it constructs

could be the :shadow-cljs alias has a :replace-paths? anything that would remove the default :paths really?

yes

there was a :paths ["src/main"]

😄

damn

thanks that fixes it then!

while investigating I read that these js files are going to go through advanced compilation?

depends on how they are written, but probable yes

ESM import/export goes through :advanced

CommonJS require/module.exports does not

It contains this:

import Quill from 'quill';

const BlockEmbed = Quill.import('blots/block/embed');

class DividerBlot extends BlockEmbed {
  static blotName = 'divider';
  static tagName = 'hr';
}

Quill.register(DividerBlot);

(ns foo.bar
  (:require
    [shadow.cljs.modern :refer (defclass)]
    ["quill$default" :as Quill]))

(def BlockEmbed (Quill/import "blots/block/embed"))

(defclass DividerBlot
  (extends BlockEmbed)
  
  (constructor [this]
    (super)))

(set! DividerBlot -blotName "divider")
(set! DividerBlot -tagName "hr")

(Quill/register DividerBlot)

currently constructor is required, so if it has different arity you'd need to provide that

I actually tried this after finding defclass with some research but it didn't work

still need to add the no-constructor support for defclass

nothing strange about it. the closure compiler depends on protobuf v3 and is not compatible with v4

sounds like they maybe introduced some syntax the closure compiler doesn't like

thats unfortunately a bit common nowadays

Thanks. Any possible solution?

Which syntax might that be?

I see a #modified as a variable name

I guess I can try to recompile with ES6 as target

And not ES2020

thats not relevant. there is no fix, as it fails to parse the file and cannot process it any further.

#modified is syntax for private fields. that is indeed not supported.

https://github.com/google/closure-compiler/issues/2731

only option is to either not use that package or switch to use a different tool for JS processing, see https://shadow-cljs.github.io/docs/UsersGuide.html#js-provider-external

Thank you!