允许用户管理npm模块的依赖版本

Question

I'm building a module that will have THREE.js as a dependency. I'm trying to work out the best way to include THREE as a dependency and make it accessible to the module and users of the module (users will need access to the THREE library within their projects). There are two ways I have figured out of making this work:

One:

Add THREE as a dependency of the module, import the whole library in the module and add it as a global variable like so:

import * as THREE from 'three'; 
window.THREE = THREE;

The disadvantage here is that I am responsible for what version of THREE is used, and also that the whole library is imported (THREE has recently switched to a modular build so it is no longer neccessary to include the whole library).

Two:

Add THREE as a dependency of the module and require users to add it as a dependency of their project. The idea here is that I can now import only what I need from the project:

import { Scene, Camera } from 'three'; 

And users can import what they need in their project, resulting in smaller file size.

The problem here is that now there are two copies of THREE installed, which are potentially different and incompatible versions. Is there any way to point my module to the top level module so that they can manage the version of THREE that is installed?

Answer 1

The way I ve seen it done is similar to this, but I never had to do something like it in production, so I do not know personally of its strength:

main.js:

'use strict';
const three = require('three'),
    mod = require('yourModule');

mod.init(three);
//...

yourModule.js:

'use strict';
let three = {};
function init(t) {
    three = t;
}
//...
modules.export = {
    init: init
    //...
};

Or

main.js:

'use strict';
const three = require('three'),
    mod = require('yourModule')(three);

yourModule.js:

'use strict';
module.exports = (three) => {
    //...
};