Make an es6 version also

[OSG-Proj]

Note: for support questions, please use one of these channels: stackoverflow or slack

For bug reports and feature requests for the Swift client, please open an issue there.

For bug reports and feature requests for the Java client, please open an issue there.

You want to:

• [] report a bug
• [x ] request a feature

Current behaviour

What is actually happening?
I can see that this is a commonjs module, webpack supports interoptability across modules, but isnt recommended.

Steps to reproduce (if the current behaviour is a bug)

Note: the best way (and by that we mean the only way) to get a quick answer is to provide a failing test case by forking the following fiddle.

Expected behaviour

What is expected?
There should be es6 exports instead of module.exports for use in the browser, due to the fact socket.io-client is a client side portion of socket.io.

Setup

• OS: windows 10
• browser: chrome
• socket.io version: 2.3.0

Other information (e.g. stacktraces, related issues, suggestions how to fix)

[darrachequesne]

Sounds reasonable. Let's add this 👍

[eouia]

Although bundling(webpack, browsify,...) would be still a good but legacy approach, a native ES6 module supporting would be needed also. I voted to this.

[MickL]

Angular CLI even throws a warning:

Warning: /folder/myfile.ts depends on 'socket.io-client'. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

[darrachequesne]

This was implemented in 16b6569, included in socket.io-client@4.3.0.