Nodes: Mark as effectful for Webpack.

[CodyJasonBennett]

Fixes: #27076

Description

Configures sideEffects to exclude three/nodes from coarse module skipping prior to tree-shaking. Since #26881, Nodes are effectful and cannot be individually tree-shaken.

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

Filesize dev	Filesize PR	Diff
667.4 kB (165.9 kB)	667.4 kB (165.9 kB)	+0 B

🌳 Bundle size after tree-shaking

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

Filesize dev	Filesize PR	Diff
449.3 kB (108.8 kB)	449.3 kB (108.8 kB)	+0 B

[emnul]

Thanks for the fix! I was running into issues with my vite build due to this.

[hybridherbst]

Out of curiosity, was it even intentional that #26881 now requires these additional steps? I can't see a mention of it in the original PR so can only assume that was by accident. I think it would be better if there's no additional configuration needed.

[mrdoob]

Out of curiosity, was it even intentional that #26881 now requires these additional steps? I can't see a mention of it in the original PR so can only assume that was by accident. I think it would be better if there's no additional configuration needed.

/ping @sunag

[hybridherbst]

Seems vite ignores both exports and sideEffects in locally referenced dependencies:

• Module resolution of declared exports doesn't work for local package vitejs/vite#15412

[LeviPesin]

Out of curiosity, was it even intentional that https://github.com/mrdoob/three.js/pull/26881 now requires these additional steps? I can't see a mention of it in the original PR so can only assume that was by accident. I think it would be better if there's no additional configuration needed.

I'm pretty sure Nodes became effectful since at least the introduction of node chaining (I've explicitly noted that tree-shaking wouldn't work now in #25526). I've also suggested a possible workaround in that issue.