You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 15, 2021. It is now read-only.
It seems that when one tries to use the node HTTP module req.setTimeout and req.abort() are undefined. This might be expected behavior except for the fact that the same bit of code works if run through browserify first. I have created a repo with the minimal code to reproduce the issue.
What does meteor do with node-stubs that is different enough from browserify to cause these methods to nor work?
stacktrace:
Uncaught TypeError: req.setTimeout is not a function
at Object.click button (main.js:49)
at blaze.js:3775
at Function.Template._withTemplateInstanceFunc (blaze.js:3744)
at Blaze.View.<anonymous> (blaze.js:3774)
at blaze.js:2617
at Object.Blaze._withCurrentView (blaze.js:2271)
at Blaze._DOMRange.<anonymous> (blaze.js:2616)
at HTMLButtonElement.<anonymous> (blaze.js:863)
at HTMLBodyElement.dispatch (jquery.js:4722)
at HTMLBodyElement.elemData.handle (jquery.js:4390)
The text was updated successfully, but these errors were encountered:
It seems that when one tries to use the node HTTP module
req.setTimeout
andreq.abort()
are undefined. This might be expected behavior except for the fact that the same bit of code works if run through browserify first. I have created a repo with the minimal code to reproduce the issue.https://github.com/TechplexEngineer/meteor-http-browserify-repro/tree/master
What does meteor do with node-stubs that is different enough from browserify to cause these methods to nor work?
stacktrace:
The text was updated successfully, but these errors were encountered: