Exclude three.js from build

[stefnotch]

I just noticed that I forgot to exclude three.js from the built output. This made it significantly larger than it should have been.
This fixes that by marking three.js as an external dependency. And it moves it to peerDependencies.

However, it introduces a new problem. The built file now starts with the following, since it's

1. a module
2. uses Raycaster and Vector2 from three.js
3. doesn't know how to import three.js

import{Raycaster as a,Vector2 as h}from"three";

In Node.js or with any modern build tool, this works quite fine. "three" is specified in the package.json, and thus, Node/the build tool knows what to do and where to find it (node_modules).

However, web browsers don't. This effectively breaks the examples, since the examples don't go through a compile step.

There is a really nice proposal called "import maps", which solves that. It lets you specify what dependencies there are and how to get them. And Chrome already supports them. But other browsers aren't quite that far yet.

[markuslerner]

Hi @stefnotch,

thank you for making this change!

I fixed the examples using import maps and a polyfill for import maps. The three.js examples also do it like that. I also created a new release v1.3.0.

I hope this also fixes issues #10 and #12.

[stefnotch]

Sweet 👍
I didn't know that it was possible to polyfill import maps. That's nice indeed!