[@types/three] Version 0.183.1 - THREE.Scene in VSCode points to a wrong object

[zbizaca]

import * as THREE from "three";
class ....
  private scene: THREE.Scene<THREE.Object3DEventMap>;

// Type 'Scene' is not generic.ts(2315)

It points to

    interface Scene {
        environmentNode?: Node<"vec3"> | null | undefined;
        backgroundNode?: Node | null | undefined;
        fogNode?: Node | null | undefined;
    }
}

in
node_modules/@types/three/src/renderers/common/nodes/NodeManager.d.ts

Not the Scene generic class.

Note: it works fine in version 0.182.1

[typescript-bot]

Thanks for the discussion about "three", some useful links for everyone:

• npm
• DT
• Related discussions

Pinging the DT module owners: @joshuaellis, @Methuselah96.

[Methuselah96]

Hmm, looks like the Scene generic got removed by accident in three-types/three-ts-types#2016. I will add it back.

[Methuselah96]

Added back by three-types/three-ts-types#2063, which will be released with @types/three@0.184.0

It looks like VSCode is finding both definitions, it's not choosing one over the other?

[zbizaca]

The selection is determined by the TypeScript, no VSCode, is what I understand. Is it the order of listing that changed?

[zbizaca]

it was this change:
export class Scene extends Object3D {

Does it make sense to have the generic? I can just remove it 🙂

[Methuselah96]

Removing it makes sense for your use case