The official examples run in the browser without being bundled first, so use an importmap to tell your browser what three/addons/ means when it encounters it in an import statement. It’s an alias pointing to a resource.
If you are importing using npm and using a build tool, then depending on whether your environment understands the package.json → exports option, (see line 8 and 15)
then it will internally redirect any import statement containing the word addons to the ./examples/jsm/Addons.js script, which then contains more information about how your environment can resolve the resource you are referencing.
or,
If your development environment doesn’t understand the package.json → exports option, then you can continue to use three/examples/jsm/...
eg,
<script type="module">
import * as THREE from 'three'
import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls.js'
import Stats from 'three/examples/jsm/libs/stats.module.js'
// ... etc