ability to require peerjs inside the node repl

[natesire]

I am able to load npm modules inside my node repl. But when I try to load peerjs I receive a window error. This might not be a bug. Maybe just an idea. This way, we can make it easy to try ideas out and play with the code. What do you think? Does peerjs need to rely on the window object to work. If so, should I try using the npm window to do it?

var pj=require('peerjs'); Uncaught ReferenceError: window is not defined at Object.parcelRequire.tI1X../adapter_factory.js (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:38:161) at f (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:1:468) at p (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:1:544) at Object.parcelRequire.sXtV.webrtc-adapter (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:40:161) at f (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:1:468) at p (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:1:544) at Object.parcelRequire.I31f../adapter (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:42:75) at f (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:1:468) at p (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:1:544) at Object.parcelRequire.BHXf.peerjs-js-binarypack (/home/colombia/WebstormProjects/chat-room/node_modules/peerjs/dist/peerjs.min.js:44:285)

[natesire]

???

Calendly.com/natesire Cell: +1.727.359.7503

On Sat, Nov 21, 2020, 6:44 AM Charlie Crystle [email protected] wrote:

bump

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/peers/peerjs/issues/677#issuecomment-731567783, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABC4UPBQCWKHOEDMNLJYL53SQ6RZBANCNFSM4NNKO7HQ .

[StoneCypher]

peerjs is attempting to reference the browser's window global. node does not have one of these.

This means that until the library is taught to not need that, it won't actually work in node.