new Peer only works if using window.Peer in angular application

Hi.

I am importing peerjs npm package into my client-side application vie plugins capability in webpack:

... let plugins = [ new webpack.ProvidePlugin({ $: "jquery", jQuery: "jquery", Peer: "peerjs" ...

Until recently, I was able to just call var peer = new Peer(idService.generateId(), config.peerConfig); and the Peer object would be instantiated for me. Now with a recent update, only calling a window.Peer as a constructor results in expected behavior, while simply trying to call new Peer(... will result in Peer is not a constructor error.

Did I miss some change announcement or the way I import it is wrong for .ts-based peerjs implementation?

[maxpavlov]

@kidandcat you have a terrific intuition, man 👍

new webpack.ProvidePlugin({
		$: "jquery",
		jQuery: "jquery",
		Peer: ['peerjs','default']
	}),

Importing with default property specified has fixed the problem of having to use window.Peer. Thank you.

[kidandcat]

Are you doing this?

For importing the default export of an ES2015 module, you have to specify the default property of module.

See the Vue example:

          Vue: ['vue/dist/vue.esm.js', 'default']