ES Module (ESM) version of threebox

[danvk]

As of r106 ES modules are the preferred way to use THREE.js. I'd like to import THREE.js in my own code as an ES module, but threebox uses its own bundled version of three.js, which I imagine will cause issues.

It would be great if threebox used the ESM version of THREE.js rather than bundling its own. Or, alternatively, gave the user some way to bring your own THREE.js.

[peterpolman]

There is a way to change the baked in three.js version; Try to replace the ./src/three.js file with a version of your choice and run the build command as defined in ./package.json.

npm run build

This will compile a new minified threebox file containing your specified three.js version. You can require this in your app. Beware for conflicts when you upgrade three.js in threebox, the threebox code might not be ready for the latest three.js changes:)

[danvk]

That's not usually how dependencies are handled with NPM :) It would be better if threebox declared its dependency on three.js, rather than bundling it. This would let my app and threebox share a common version.

[peterpolman]

I know. But you asked for a way to bring your own three.js version. This is a way:)

…

On Fri, 4 Oct 2019 at 00:50, Dan Vanderkam ***@***.***> wrote: That's not usually how dependencies are handled with NPM :) It would be better if threebox declared its dependency on three.js, rather than bundling it. This would let my app and threebox share a common version. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#75?email_source=notifications&email_token=AASEXRZF7ZC7ZGETZDZYM7LQMZZJTA5CNFSM4I42Z232YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAJ2NUY#issuecomment-538158803>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASEXR2Q2VVTLVJTXHVNGC3QMZZJTANCNFSM4I42Z23Q> .