Currently, there is no implementation of urlfetch for Node.js so you would have to use the standard HTTP library <https://nodejs.org/api/http.html> or other libraries to issue HTTP requests.
I created a feature request on the issue tracker website <https://issuetracker.google.com/111182003> which will get forwarded to engineering. You can click on the star next to the request title on the top of the page to mark that you are interested in the feature and receive email updates. However there are no ETAs or guarantees of implementation for feature requests. Regarding performance, all HTTP requests, whether urlfetch is used or not, are issued using App Engine’s URL Fetch service <https://developers.google.com/apps-script/reference/url-fetch/> for efficiency and scaling purposes. Meaning performance will not differ while using native libraries or urlfetch. One advantage that urlfetch has is that it provides you with an interface to make asynchronous requests <https://cloud.google.com/appengine/docs/standard/python/issue-requests>. On Tuesday, July 3, 2018 at 2:01:26 AM UTC-4, Aleksander Efremov wrote: > > All outbound requests in the "appengine" of "python" and "go" issue via > "urlfetch" service. But for "node.js" it isn't available. There is > improvements on using the "urlfetch" service instead of a native libraries > in "python" and "go"? And why it isn't implemented for "node.js"? > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/08ee0399-ace7-456c-bc51-bb237834ade6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
