You need to await for json. var sentiments = await fetch(SEN_URL, {method: “POST”, body: {“data”: [{“text”: “I love you”}, {“text”: “I hate you”}]}}) //Here await sentiments.json() Also you can make request with JSON.stringify() for body. And it will be easier to manage your js object. Like this: var data = {data: [{text: “I love you”}, … Read more
You need to stringify your body: let params: RequestInit = { headers: headers, method: “PUT”, body: JSON.stringify(body) }
Axios doesn’t address that situation so far – you can try: process.env.NODE_TLS_REJECT_UNAUTHORIZED = ‘0’; BUT THAT’S A VERY BAD IDEA since it disables SSL across the whole node server. Or, you can configure axios to use a custom agent and set rejectUnauthorized to false for that agent as mentioned here. Example: const https = require(‘https’); … Read more
Fetch 3.0 is designed for using esmodules instead of commonjs. Therefore you have to make sure you import it into a module. For example: to import it to app.js : Add “type”:”module” in your package.json and then import it. For importing it to other files or app.js even, you can also change the extension from … Read more
Browser restricts HTTP requests to be at the same domain as your web page, so you won’t be able to hit imgur api directly from the browser without running into CORS issue. I am converting images to base64 strings and sending them via Postman works great. That’s because Postman is not a browser, so is … Read more
What I found is that the latest version of node-fetch changed to ES modules by default. You can: Uninstall the current version of node-fetch with npm uninstall node-fetch Install the second version: npm install node-fetch@2 It has worked for me!
README.md says: Use native stream for body, on both request and response. And sources indicate it supports several types, like Stream, Buffer, Blob… and also will try to coerce as String for other types. Below snippet shows 3 examples, all work, with v1.7.1 or 2.0.0-alpha5 (see also other example further down with FormData): let fetch … Read more
The other way to do is to set your own agent to the fetch call. const fetch = require(‘node-fetch’); const https = require(‘https’); const httpsAgent = new https.Agent({ rejectUnauthorized: false, }); const response = await fetch(url, { method: ‘POST’, headers: headers, body: body, agent: httpsAgent, });
You should be able to pass along cookies by setting it in the header of your request: const opts = { headers: { cookie: ‘accessToken=1234abc; userId=1234’ } }; const result = await fetch(`/some/url`, opts);
From the Upgrade Guide node-fetch was converted to be a ESM only package in version 3.0.0-beta.10. node-fetch is an ESM-only module – you are not able to import it with require. Alternatively, you can use the async import() function from CommonJS to load node-fetch asynchronously: // mod.cjs const fetch = (…args) => import(‘node-fetch’).then(({default: fetch}) => … Read more