How do I use a proxy with Node and ESM?
up vote
0
down vote
favorite
In the olden days I had something like this...
const HttpsProxyAgent = require("https-proxy-agent");
new HttpsProxyAgent(URL)
However when I convert to ESM...
import HttpsProxyAgent from "https-proxy-agent";
// Also tried
// import * as HttpsProxyAgent from "https-proxy-agent";
new HttpsProxyAgent(URL)
I get...
(node:7856) UnhandledPromiseRejectionWarning: TypeError: HttpsProxyAgent is not
a constructor
So how do I accomplish this now? Is there a native ES6 proxy that node supports?
node.js
asked Nov 21 at 19:55
JGleason
1209
add a comment |
up vote
0
down vote
favorite
In the olden days I had something like this...
const HttpsProxyAgent = require("https-proxy-agent");
new HttpsProxyAgent(URL)
However when I convert to ESM...
import HttpsProxyAgent from "https-proxy-agent";
// Also tried
// import * as HttpsProxyAgent from "https-proxy-agent";
new HttpsProxyAgent(URL)
I get...
(node:7856) UnhandledPromiseRejectionWarning: TypeError: HttpsProxyAgent is not
a constructor
So how do I accomplish this now? Is there a native ES6 proxy that node supports?
node.js
asked Nov 21 at 19:55
JGleason
1209
Exporting any sort of function asmodule.exportsin CommonJS became somewhat of a bad habit when ES6 module syntax was introduced to the specification. It's not guaranteed by the specification thatimport * as ...will actually retain the function and not just its properties. But to indirectly answer your question,console.log(HttpsProxyAgent);afterimport HttpsProxyAgent from 'https-proxy-agent';and that output should tell you what you need to know.
– Patrick Roberts
Nov 21 at 20:00
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In the olden days I had something like this...
const HttpsProxyAgent = require("https-proxy-agent");
new HttpsProxyAgent(URL)
However when I convert to ESM...
import HttpsProxyAgent from "https-proxy-agent";
// Also tried
// import * as HttpsProxyAgent from "https-proxy-agent";
new HttpsProxyAgent(URL)
I get...
(node:7856) UnhandledPromiseRejectionWarning: TypeError: HttpsProxyAgent is not
a constructor
So how do I accomplish this now? Is there a native ES6 proxy that node supports?
node.js
asked Nov 21 at 19:55
JGleason
1209
In the olden days I had something like this...
const HttpsProxyAgent = require("https-proxy-agent");
new HttpsProxyAgent(URL)
However when I convert to ESM...
import HttpsProxyAgent from "https-proxy-agent";
// Also tried
// import * as HttpsProxyAgent from "https-proxy-agent";
new HttpsProxyAgent(URL)
I get...
(node:7856) UnhandledPromiseRejectionWarning: TypeError: HttpsProxyAgent is not
a constructor
So how do I accomplish this now? Is there a native ES6 proxy that node supports?
node.js
node.js
asked Nov 21 at 19:55
JGleason
1209
asked Nov 21 at 19:55
JGleason
1209
asked Nov 21 at 19:55
JGleason
1209
asked Nov 21 at 19:55
JGleason
1209
asked Nov 21 at 19:55
JGleason
1209
1209
Exporting any sort of function asmodule.exportsin CommonJS became somewhat of a bad habit when ES6 module syntax was introduced to the specification. It's not guaranteed by the specification thatimport * as ...will actually retain the function and not just its properties. But to indirectly answer your question,console.log(HttpsProxyAgent);afterimport HttpsProxyAgent from 'https-proxy-agent';and that output should tell you what you need to know.
– Patrick Roberts
Nov 21 at 20:00
add a comment |
Exporting any sort of function asmodule.exportsin CommonJS became somewhat of a bad habit when ES6 module syntax was introduced to the specification. It's not guaranteed by the specification thatimport * as ...will actually retain the function and not just its properties. But to indirectly answer your question,console.log(HttpsProxyAgent);afterimport HttpsProxyAgent from 'https-proxy-agent';and that output should tell you what you need to know.
– Patrick Roberts
Nov 21 at 20:00
Exporting any sort of function as
module.exports in CommonJS became somewhat of a bad habit when ES6 module syntax was introduced to the specification. It's not guaranteed by the specification that import * as ... will actually retain the function and not just its properties. But to indirectly answer your question, console.log(HttpsProxyAgent); after import HttpsProxyAgent from 'https-proxy-agent'; and that output should tell you what you need to know.– Patrick Roberts
Nov 21 at 20:00
Exporting any sort of function as
module.exports in CommonJS became somewhat of a bad habit when ES6 module syntax was introduced to the specification. It's not guaranteed by the specification that import * as ... will actually retain the function and not just its properties. But to indirectly answer your question, console.log(HttpsProxyAgent); after import HttpsProxyAgent from 'https-proxy-agent'; and that output should tell you what you need to know.– Patrick Roberts
Nov 21 at 20:00
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419610%2fhow-do-i-use-a-proxy-with-node-and-esm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Exporting any sort of function as
module.exportsin CommonJS became somewhat of a bad habit when ES6 module syntax was introduced to the specification. It's not guaranteed by the specification thatimport * as ...will actually retain the function and not just its properties. But to indirectly answer your question,console.log(HttpsProxyAgent);afterimport HttpsProxyAgent from 'https-proxy-agent';and that output should tell you what you need to know.– Patrick Roberts
Nov 21 at 20:00