PeerJs Creating Default Connection on load

[cohenstyle]

I'm importing PeerJS from the NPM module and using it with custom stun servers. This appears to work fine.
But when the app loads it makes an initial connection using the default servers before my code ever starts using the library.
How can I disable this?

[cohenstyle]

It looks like it's likely part of the process to determine what the browser supports. Is there a way to make a best guess without making a connection?

[AlonBru]

Can you include the code you are using or a minimal reproduction example?
otherwise it may be a bit hard to tell exactly what happens and why :), and
whether this is a bug or otherwise

[cohenstyle]

It's been a while since I've used peerjs due to the other bug (can't send data in order.)
But I believe the code is:
import { Peer } from "peerjs";

Importing the library triggers a connection to a test server.

[AlonBru]

I have created a codesandbox to try and recreate this, but had not noticed it happening just by importing.
Feel free to edit it if you're still interested in chasing this issue.

[cohenstyle]

Ah sorry, my mistake. You have to create the Peer object.
The issue is in this line: https://github.com/peers/peerjs/blob/master/lib/util.ts#L62
It's called here: https://github.com/peers/peerjs/blob/master/lib/peer.ts#L211
When checking to see what's supported, a connection is made using the default config regardless of the config of the Peer connection.
This connects to Google and/or PeerJS servers regardless of which stun and turn servers the developer wants to use for the remainder of the app.
Thank you very much for looking into this.

[cohenstyle]

This one may be higher priority though (I'm haven't followed the calls to determine why reliable is not being passed): #746

[Niksac]

I also noticed this behaviour today.
Is there any way to prevent this?

Just loading the PeerJS files without any additional code will connect to google and Peerjs servers.
This is problematic when under GDPR or similar.