Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read property 'connectTimeoutTimer' of undefined #49

Open
traviswimer opened this issue Dec 6, 2016 · 1 comment
Open

Cannot read property 'connectTimeoutTimer' of undefined #49

traviswimer opened this issue Dec 6, 2016 · 1 comment

Comments

@traviswimer
Copy link

I'm getting a strange error that seems to be caused by some conflict between this module and https://github.com/desmondmorris/node-twitter

TypeError: Uncaught error: Cannot read property 'connectTimeoutTimer' of undefined
    at ConnectTimeoutAgent.createSocket (/path/to/project/node_modules/html-metadata/node_modules/preq/index.js:21:46)
    at ConnectTimeoutAgent.Agent.addRequest (_http_agent.js:157:10)
    at new ClientRequest (_http_client.js:160:16)
    at Object.exports.request (http.js:31:10)
    at Object.exports.request (https.js:199:15)
    at Request.start (/path/to/project/node_modules/twitter/node_modules/request/request.js:744:32)
    at Request.write (/path/to/project/node_modules/twitter/node_modules/request/request.js:1421:10)
    at end (/path/to/project/node_modules/twitter/node_modules/request/request.js:551:18)
    at Immediate.<anonymous> (/path/to/project/node_modules/twitter/node_modules/request/request.js:580:7)
    at runCallback (timers.js:637:20)
    at tryOnImmediate (timers.js:610:5)
    at processImmediate [as _immediateCallback] (timers.js:582:5)

The strange thing is that this error is thrown when I make a request with node-twitter. It seems html-metadata never actually needs to be used, this error will be thrown if it is simply require-ed.

Sorry if this isn't the right place to post this, but I figured I would start here since I'm not actually sure where the source of this problem is.

@d00rman
Copy link
Contributor

d00rman commented Dec 16, 2016

@traviswimer Which version of node and html-metadata are you using? Do you see this error consistently or only for certain requests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants