they are likely not identical modules

do you include three.js via some cdn script tag or so?

the error you get is from three.js, so you'll need to investigate where you are getting multiple three.js versions from

a build report might help https://shadow-cljs.github.io/docs/UsersGuide.html#build-report

I didn’t include three.js myself, but I guess it probably comes in as a transitive dependency in several places. This the package-json:

{
  "dependencies": {
    "create-react-class": "^15.7.0",
    "katex": "0.12.0",
    "markdown-it": "12.3.2",
    "markdown-it-block-image": "0.0.3",
    "markdown-it-footnote": "3.0.3",
    "markdown-it-texmath": "0.9.7",
    "markdown-it-toc-done-right": "4.2.0",
    "punycode": "2.1.1",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "react-force-graph": "^1.43.0"
  }
}

you can also check npm list and look for duplicates of three

npm list just gives the items in the package.json

and the report doesn’t contain duplicates, or at least I am unable to see ascertain their existence :man-shrugging:

could also be any other package bundling their own version of three.js

look for larger than normal packages

that seems likely

Aframe seems abnormally large, but I’m not really sure what to do with that knowledge.

you can try https://shadow-cljs.github.io/docs/UsersGuide.html#js-resolve

so :js-options {:resolve {"three" {:target :global :global "THREE"}}}

that will make shadow-cljs not include the three npm package at all and instead use the global variable THREE

if a package already bundles three and provides this that might work?

no clue if a-frame already bundles it but could be a try

yes, it indeed seems to do that

thank you! Gonna try that out!

So that successfully removes the warning about the duplicate three.js, but the module load error is still present (and it actually crashes Firefox completely for me, had to force-quit). Do you have any idea how to debug something like that…?

I mean this error. I can’t even view the compiled JS, since Firefox crashes when I attempt to do so… not that I think it would help much.

that is not enough info. as the text says any additional errors are whats relevant. not the yellow warnings

I now also updated a bunch of different dependencies and now the problem is suddenly not present… 🤷

So I guess that’s good at least!

Thanks for answering my clueless questions