WebGPURenderer: Tree-shaking 1/2

[sunag]

Related issue: #28328

Description

This PR prepares the architecture for three.webgpu.nodes.js which will be done in another PR, some chaning methods have been removed in favor of tree-shaking and should be imported now.

We have StandardNodeLibrary all the Three.js shader inclusions from Materials to ToneMappings, this static part is only assigned to three.webgpu.js which will not have full support for three-shaking.

This is a big change and may impact some existing projects, but I think it will be the last big change until release.

• Move NodeMaterials out of Nodes
• Create NodeLibrary and StandardNodeLibrary support
• Added support to NodeLibrary
• Move NodeLoader out of Nodes
• Create TSLBase.js
• Revisions 1/2
• Create TSL.js
• Revision Nodes
• Revision Examples
• Revision NodeLoader
• Revisions 2/2

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

Filesize dev	Filesize PR	Diff
685.4 kB (169.7 kB)	685.4 kB (169.7 kB)	+0 B

🌳 Bundle size after tree-shaking

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

Filesize dev	Filesize PR	Diff
462 kB (111.4 kB)	462 kB (111.4 kB)	+0 B

[RenaudRohlinger]

Related: #29156

[WestLangley]

some chaining methods have been removed in favor of tree-shaking

Some TSL operators can now be chained and others cannot. IMO, this results in a confusing API.

Users will be annoyed that they can't remember which ones can, and which ones cannot, be chained.

Can we solve this -- even if it hurts tree-shaking somewhat?

[sunag]

Some TSL operators can now be chained and others cannot. IMO, this results in a confusing API.

@WestLangley Can you list the TSL operators you are currently using that are no longer available? This might help me get a second understanding of the issue.

[WestLangley]

@sunag I rewrote my code to accommodate this PR, but I believe this was the original set.

bloom
sepia
posterize
dof
saturation
vignette

[RenaudRohlinger]

There’s also more here: #29238.

Also I would say that all of these feel quite niche and case-specific, making them more suitable as third-party nodes.

And if a developer wants to use them as chainabable it is still possible in user-land through addMethodChaining.

[mrdoob]

@sunag I rewrote my code to accommodate this PR, but I believe this was the original set.

bloom
sepia
posterize
dof
saturation
vignette

Maybe these nodes should be addons instead of being in core? Maybe that'll help to understand what's chainable and whats not.

[sunag]

Maybe these nodes should be addons instead of being in core?

Would we then have two imports? Or would it be something else?
Some nodes that are in the core are not chainable like texture, uniform, vec*, ...

import { texture, uniform } from 'three/tsl';
import { saturation, posterize } from 'three/addons/nodes/TSLAddons.js';

[mrdoob]

Or something like this...

import { texture, uniform } from 'three/tsl';
import { posterize } from 'three/addons/tsl/display/posterize.js';
import { saturation } from 'three/addons/tsl/display/saturation.js';

[sunag]

I think I need more one day to review some items in this PR 😇

[sunag]

I think I need more one day to review some items in this PR 😇

@mrdoob Done! :)