import fabric using externals vs from node_modules

[Shashank-Bhatt1]

I got into one issue and found similar problem here when trying to use fabric as modular vs global way.

i am working on package and i need to import fabric, but i need to be able to do so that for any of bundler/global way it should be correct, as i am not sure whether parent app /package have it already available in global scope or not.

1. when using import fabric from 'fabric' statement while using modular way, it expects to destructure like {fabric}
2. But when i use above in umd way by keeping fabric as externals in vite.config (or webpack.config) then import {fabric} from 'fabric' creates an issue because at that time fabric is global and directly needed as fabric and not {fabric}.

Is there any common workaround for this so that using it in any way does not require code modification? I also tried using es build entry of vite bundler instead of umd but still same problem occurs.

[zhe-he]

There’s always one that suits you.

import * as fabric from 'fabric'  

const  f = require('fabric')

window.fabric.fabric = window.fabric;

[Shashank-Bhatt1]

I checked and imported like that and also added 3rd line but it didn't not work. I am still using fabric 5.x

[zhe-he]

I checked and imported like that and also added 3rd line but it didn't not work. I am still using fabric 5.x

Sorry. The methods I provided are all based on version 6.0.

[asturur]

I have been trying to import fabric as an external dependency in a bundler and i had some issues as well. I didn't come back to it yet.
I'm using rollup and a very simple setup