"no exported member" errors when using NodeNext module/moduleResolution in TypeScript

• three version: n/a
• @types/three version: n/a
• three-stdlib version: 2.29.4

Problem description:

I ran into this bug and it took a while to figure out. It turns out that this library (as well as threes-stdlib) are not compatible with "NodeNext" module/moduleResolution, e.g. if you tsconfig.json looks like this:

    "module": "NodeNext",
    "moduleResolution": "NodeNext",

And you try to use this library like this:

Code:

import { GLTF, GLTFLoader } from 'three-stdlib'

You will get compile errors via TSC like this:

src/Scene.tsx:17:16 - error TS2305: Module '"three-stdlib"' has no exported member 'GLTFLoader'.

You can work around the bug by switching your tsconfig.json to something like this instead:

    "module": "ESNext",
    "moduleResolution": "Node",

Relevant code:

Included in the above description.

Suggested solution:

I suspect there is some way to fix this? But I do not yet know. One clue is that @react-three/fiber and @react-three.drei work properly with these tsconfig.json settings.

Start by reproducing the reported import from src/Scene.tsx with the NodeNext settings in tsconfig.json and run TSC. Compare the package's exported types with the behavior under NodeNext module resolution. Done means GLTF and GLTFLoader compile as exported members without requiring the ESNext/Node workaround.