Could not resolve "three/examples/jsm/exporters/GLTFExporter" while building three.js app

[soadzoor]

Describe the bug

I upgraded my app from r137 to r138, and since then I have the following errors (a lot of similar ones):

I checked the migration guide (137->138), but it seems it doesn't say anything about this. The strange thing, is that the files are still there, so I don't know why it says "it was not found". I'm using esbuild for bundling the js file, if that matters (but it worked flawlessly with r137, so I'm pretty sure something has changed with three.js, not esbuild ).

Does anyone has an idea what might be the problem?
Thanks

[soadzoor]

(might be related to this one? I don't know: #23625 )

[marcofugaro]

@soadzoor if you use esbuild, it requires you to import using the .js extension as the ESModule spec says:

import { GLTFLoader } from 'three/examples/jsm/loaders/GLTFLoader.js'

[soadzoor]

@marcofugaro Hm, that seems to be working, thanks. But still not sure what changed. 🤔

[marcofugaro]

But still not sure what changed. 🤔

three.js is now a proper ES Module 🙂

three.js/package.json

Line 5 in 8e1b509

"type": "module",