Uncaught TypeError when accessing OrbitControls from unpkg.com

With version 128, the following code:

<script type="module">
import * as THREE from 'https://unpkg.com/three@0.128.0/build/three.module.js';
import { OrbitControls } from 'https://unpkg.com/three@0.128.0/examples/jsm/controls/OrbitControls.js';
</script>

causes the following error:

Uncaught TypeError: Failed to resolve module specifier "three". Relative references must start with either "/", "./", or "../".

It worked fine in 127 though.

[x1911]

@Mugen87 https://jsfiddle.net/x1911/3x0rv8y9/

it stucks in gltf loader loading

[donmccurdy]

Looks like unpkg has an experimental ?module option you can add to the URL that allows it to work with three.js too:

https://discourse.threejs.org/t/importing-jsm-modules-using-explicut-urls-no-longer-works-for-basic-jsfiddle-examples-since-r128/25858/3

I’d be curious if you are seeing loading time differences between Skypack and Unpkg?

That said, yes, local development will allow you to work much faster. So far https://www.skypack.dev/ seems like one of the more user-friendly options. Then you can deploy to something with a CDN cache (e.g. netlify handles this automatically) when you are finished working locally.