TypeError: this.pingIntervalTimer.refresh is not a function
See original GitHub issueDescribe the bug There seems to be some dependency-issues:
/app/node_modules/browser-sync/node_modules/engine.io/build/socket.js:109 this.pingIntervalTimer.refresh(); ^ TypeError: this.pingIntervalTimer.refresh is not a function at Socket.onPacket (/app/node_modules/browser-sync/node_modules/engine.io/build/socket.js:109:40)
[…]
To Reproduce
Socket.IO server version: 2.0.3
Socket.IO client version: 1.4.8
Node version: 8.9.3
NPM version: 5.5.1
Platform: OS: Ubuntu
Additional context Running in a docker container. Added to a project based on open source project openstf/stf, so the dependencies looks alike.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
socket.io TypeError: socket.on is not a function - Stack Overflow
To fix that you can just add socket to the arguments on your callback function. Like this: io.on('connection',function(socket) { console.
Read more >Introduction to Sockets.IO in Node.js - GeeksforGeeks
What this code does, is it creates a function handler for Express which then gets supplied to an HTTP server. This handler responds...
Read more >"TypeError: require(...).listen is not a function" in socket.io
In this video I have shown " TypeError : require(...).listen is not a function "that you might face with connecting to ...
Read more >socket.io - npm
node.js realtime framework server. Latest version: 4.5.4, last published: a month ago. Start using socket.io in your project by running `npm ...
Read more >Timers | Node.js v19.3.0 Documentation
hasRef(); timeout.ref(); timeout.refresh(); timeout.unref(); timeout[Symbol.toPrimitive]() ... If callback is not a function, a TypeError will be thrown.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had the same issue and installing Node.js >= 10.2.0 worked for me. Thanks!
@beckbailey could you make sure you have Node.js >= 10.2.0 installed?
@peedikuubik I’m not sure copying the node_modules folder is a great idea 👼
I’m closing this, as I don’t think there is much more we can do…