Node: Document more modules.

[Mugen87]

Related issue: #29984

Description

Adding more docs.

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

	Before	After	Diff
WebGL	339.11 78.98	339.11 78.98	+0 B +0 B
WebGPU	484.86 134.6	484.85 134.59	-9 B -6 B
WebGPU Nodes	484.32 134.5	484.31 134.5	-9 B -7 B

🌳 Bundle size after tree-shaking

Minimal build including a renderer, camera, empty scene, and dependencies.

	Before	After	Diff
WebGL	465 112.04	465 112.04	+0 B +0 B
WebGPU	554.24 150.04	554.24 150.04	+0 B +0 B
WebGPU Nodes	510.12 139.75	510.12 139.75	+0 B +0 B

[Mugen87]

While writing the JSDoc there were multiple occasions where I had to document a property or parameter of a node type. The issue is in most cases I have to use the Node type because of the generic character of the node system. However, it would be more precise to additionally mentioned what data type is expected by the module.

For example a uvNode is currently documented as Node but I wonder if something like Node<vec2> would be more precise.

[sunag]

For example a uvNode is currently documented as Node but I wonder if something like Node would be more precise.

Sounds good to me 👍 This should help especially in TSL

[Mugen87]

Okay, I'll revisit this aspect with a separate PR. Adding the node type less work than writing the JSDoc in the first place^^.