Three.js now imports three.core.js?

Questions
1

I recently noticed that the simple old three.js file in the mrdoob/three.js/tree/dev/build folder on GitHub is gone. The only ones to choose from are three.module.js and three.webgpu.js, which both now import the file three.core.js, making the three.js library no longer contained in a single file (importing three.module.js triggers a request to three.core.js)

Is this a permanent thing going forward?

It would be nicer if whichever three.js version you chose didn’t make another HTTP request to three.core.js.

Can three.core.js be packed into each individual library (the standard one and the WebGPU one)?

See what I’m talking about here: three.js/build at dev · mrdoob/three.js · GitHub

2

Yes, there are 2 threejs since around r167. This makes sense since WebGPU is a completely different world. It’s better to have a threejs that focuses on WebGL and one that focuses on WebGPU. And three.webgpu.js is quite powerful. I only work with three.webgpu.js

3

I wasn’t referring to the different renderer versions of three.js, I’m referring to the fact that three.module.js and three.webgpu.js now import three.core.js, causing there to be two HTTP requests for the three.js library.

4

You can follow the PRs listed at r171

Codesplit WebGL/WebGPU entrypoints #29404

Codesplit WebGL/WebGPU entrypoints: Fix WebGPU Addons #29644