diff --git a/docs/manual/en/introduction/Import-via-modules.html b/docs/manual/en/introduction/Import-via-modules.html index f2dba4d10e506c7a6d80825dbd98c9bd6e60df94..ed7e07f2f6f6c58c5b15a9df7d0ec52fdd5bcd70 100644 --- a/docs/manual/en/introduction/Import-via-modules.html +++ b/docs/manual/en/introduction/Import-via-modules.html @@ -66,342 +66,16 @@

The core of three.js is focused on the most important components of a 3D engine. Many other components like loaders or controls are part of the examples directory. three.js ensures that these files are kept in sync with the core but users have to import them separately if they are required - for their project. However, not all files are modules which makes their usage in certain cases inconvenient. In order to address this issue, - we are working to provide all the examples as modules in the [link:https://github.com/mrdoob/three.js/tree/master/examples/jsm examples/jsm] directory. - If you install three.js via npm, you can import them like so: + for a project. You can find in the [link:https://github.com/mrdoob/three.js/tree/master/examples/jsm examples/jsm] directory an ES6 + module version for almost all example files. If you install three.js via npm, you can import them like so:

import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls.js'; -

- The following examples files are already available as modules: -

-

Note: When using code from the examples directory, it's important that all files match the version of your three.js main file. For example, it's not acceptable to use *GLTFLoader* and *OrbitControls* from R96 together - with three.js R103. You can easily keep your files in sync by using the modules from the JSM directory. If the file - is not available as a module, you can still use third-party npm packages or convert the file to a module by yourself. - In both cases, ensure the code is compatible with your three.js main file. + with three.js R103.