@marcofugaro looks good? context: https://twitter.com/bruno_simon/status/1486712639497539586

Looks good!

As an alternative we could add this to the exports list:

"./examples/fonts/*": "./examples/fonts/*",

but maybe people are importing other stuff other than jsm and fonts from the examples/ folder?

Adding only the examples/fonts folder sounds better indeed.
I'll merge and tweak.

Thanks!

3d0c8df

@mrdoob leaving this for the future (when you decide to), we could also do this for the npm users like Bruno:

import { OrbitControls } from 'three/addons';

import { helvetiker_regular } from 'three/fonts';

The current three/examples/jsm/... and three/examples/fonts/... imports would still work fine, but npm users could leaverage tree-shaking to import only OrbitControls and not the whole examples/jsm folder.

Not sure about fonts...

Feels like three would then become the new OS built-in fonts 😅

As per three/addons... Wouldn't it be this instead?

import { OrbitControls } from 'three/addons/controls/OrbitControls';

Or is there a way to "flatten" all the files in the three/addons?

Yeah, let's not tell people to import fonts from three hahaha

Or is there a way to "flatten" all the files in the three/addons?

Yes, simply by adding a file similar to src/Three.js 😇

npm users would still import only the things they need thanks to tree-shaking..

Yes, simply by adding a file similar to src/Three.js 😇

D'oh!

That sounds promising indeed. Do you want to get a PR going with that?

Sure! Let's see what people say...

So wait...

Is there a way to achieve something like this?

<script type="importmap">
	{
		"imports": {
			"three": "https://unpkg.com/three@0.137.0/",
		}
	}
</script>
    
<script type="module">
      
	import * as THREE from 'three';
	import { GLTFLoader } from 'three/addons/loaders/GLTFLoader.js';
	import { VRButton } from 'three/addons/webxr/VRButton.js';

	...
</script>

I assume you mean without renaming the examples/jsm folder.

• unpkg.com: no, it wouldn't work, unpkg only serves the actual files
• cdn.skypack.dev: yes, skypack has support for this, but only if they fix the issue with the current three.js release (skypackjs/skypack-cdn#261)

oh wait, that is not a valid import map, import maps do not automatically work like node, but some improvements are being discussed,

so with the current spec, it would look like this:

I was wrong, see #23368 (comment)

I think we should either reconsider exporting the fonts or at least export them as three/fonts (I'd prefer the former).

@LeviPesin Context? 🤔

Just thinking from one of the points of #24595 and 3d0c8df...