diff --git a/docs/manual/en/introduction/Import-via-modules.html b/docs/manual/en/introduction/Import-via-modules.html index ed7e07f2f6f6c5..99a90559b2d92c 100644 --- a/docs/manual/en/introduction/Import-via-modules.html +++ b/docs/manual/en/introduction/Import-via-modules.html @@ -66,8 +66,8 @@
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 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: + for a project. You can find them in the [link:https://github.com/mrdoob/three.js/tree/master/examples/jsm examples/jsm] directory. If you install three.js + via npm, import example files like so:
import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls.js';
@@ -77,5 +77,10 @@ Importable Examples
your three.js main file. For example, it's not acceptable to use *GLTFLoader* and *OrbitControls* from R96 together
with three.js R103.
+
+ As of THREE R117, the *examples/js* directory will not be available anymore. That means it's no longer possible to import examples files via
+ *require()* (CommonJS). Besides, it's no longer possible to include example files with the *script* tag into HTML files. The only way of importing
+ example files is via ES6 import statements.
+