Skip to content

Conversation

@Mugen87
Copy link
Collaborator

@Mugen87 Mugen87 commented Jul 29, 2025

Fixed #31527.

Description

The PR improves the JSDoc for sizeNode by highlighting that the property has no effect when using with THREE.Points and a WebGPU backend.

@github-actions
Copy link

github-actions bot commented Jul 29, 2025

📦 Bundle size

Full ESM build, minified and gzipped.

Before After Diff
WebGL 338.39
78.91
338.39
78.91
+0 B
+0 B
WebGPU 566.16
156.5
566.16
156.5
+0 B
+0 B
WebGPU Nodes 564.77
156.26
564.77
156.26
+0 B
+0 B

🌳 Bundle size after tree-shaking

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

Before After Diff
WebGL 469.82
113.62
469.82
113.62
+0 B
+0 B
WebGPU 637.38
172.47
637.38
172.47
+0 B
+0 B
WebGPU Nodes 592.02
161.71
592.02
161.71
+0 B
+0 B

@Mugen87 Mugen87 added this to the r179 milestone Jul 30, 2025
@Mugen87 Mugen87 merged commit 0f93b6f into mrdoob:dev Jul 30, 2025
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

When loading the points object in WebGPU, using the PointsNodeMaterial, setting the sizeNode is ineffective.

1 participant