Test samples with dedicated verion of Three

In the past I used references like https://rawgit.com/mrdoob/three.js/r136/examples/jsm/controls/OrbitControls.js in codepen (e.g. https://codepen.io/thogu/pen/ExwBQRp) to test functionality in a given version of three.js. Since v137 it appears that this is not working anymore since imports changed e.g. in https://rawgit.com/mrdoob/three.js/r137/examples/jsm/controls/OrbitControls.js it is

import … from “three”

whereas in v136 it was

import … from ‘…/…/…/build/three.module.js’;

Of course the relative path works but the “three” doesn’t. So I wonder how I can teste functionality with a dedicated version of three.js via codepen etc? Ideas?

The Skypack CDN (see three.js docs) should support the updated imports if you prefer to use a CDN.

Personally I typically use npm link (to use a local checkout of the three.js repo) and a bundler for this type of thing; it makes managing dependencies easier and more reliable in my opinion.