Three.js Build Structure Changes

Based on the information available, I can provide some context about the changes you've observed in the Three.js build structure.

The Three.js library has indeed undergone structural changes in its build files. The standalone three.js file is no longer available in the development branch, and instead, the library now uses a modular approach with three.module.js and three.webgpu.js that import a separate three.core.js file.

Current Structure

The current structure separates the core functionality into three.core.js which is then imported by the specialized builds:

• three.module.js - Standard ES module version
• three.webgpu.js - WebGPU-specific version

Recommendations for Usage

Given these changes, here are some recommendations:

1. Use npm installation when possible:

   BASHCopied
   npm install three

   This is the recommended approach as mentioned in the documentation, which allows you to import only what you need:

   JAVASCRIPTCopied
   // Option 1: Import the entire library
   import * as THREE from 'three';
   
   // Option 2: Import just what you need
   import { Scene } from 'three';

2. Use a bundler like webpack to package your application, which will handle these dependencies efficiently.

3. If using CDN, ensure you're using an import map to properly resolve the dependencies:

   HTMLCopied
   <script type="importmap">
   {
     "imports": {
       "three": "https://cdn.jsdelivr.net/npm/three@<version>/build/three.module.js",
       "three/addons/": "https://cdn.jsdelivr.net/npm/three@<version>/examples/jsm/"
     }
   }
   </script>

Regarding Future Changes

The documentation doesn't specifically address whether this new structure is permanent or if there will be options to have three.core.js bundled inside each build in the future.

If this is causing significant issues for your workflow, you might want to:

1. Consider using a bundler in your build process to combine these files
2. Check the Three.js GitHub repository for ongoing discussions about this change
3. Consider opening an issue on the Three.js GitHub repository to request a bundled version if this is important for your use case

Remember that when using Three.js, it's important to maintain consistent versions across all files to avoid potential issues in your application.