The dependency node-fetch was updated from 2.3.0 to 2.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

node-fetch is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The devDependency coveralls was updated from 3.0.2 to 3.0.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency nock was updated from 11.8.2 to 11.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

nock is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This issue appears to be an upstream issue with node-fetch with it's home grown promises, but this does cause errors with when attempting to use this library with others that do expect .finally() to exist.

It seems that the next version of node-fetch will support promises, so that is worth keeping an eye on.

With this release no JSON can be parsed. The error in the browser is The provided value 'stream' is not a valid enum value of type XMLHttpRequestResponseType along with being unable to parse JSON

The devDependency sinon was updated from 7.3.2 to 7.4.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The Fetch API provides a method for aborting an ongoing request. Is there a way to use this with the underlying axios engine, which relies on cancellation tokens?

There's currently stale discussion on axios to support signal.

I'm running into an issue where a GET request is failing because the axios.request(config) is being called with an invalid data property:

// config object
{
  ...
  "method": "GET",
  "data": "undefined",
  ...
}

This is due to config.data being set here to String(init.body) when init.body === undefined.

I'll submit a PR for review.

I'm getting an error when I try to create a production build with create-react-app. My package.json currently is using

"@lifeomic/axios-fetch": "bouldercare/axios-fetch"

The build (npm run build) fails with the following error.

Creating an optimized production build...

Failed to compile.



Failed to minify the code from this file: 



 	./node_modules/@lifeomic/axios-fetch/src/index.js:6 



Read more here: http://bit.ly/2tRViJ9

Any ideas why the code would fail to minify?

npmjs is missing

• 1.4.0
• 1.3.1
• 1.3.0
• 1.2.0

Can you publish those?

TypeError: Cannot read properties of undefined (reading 'name')

Its caused by isHeaders at typeUtils.js line 12.

I think it should be using optional chain operator.

const isHeaders = (headers) => headers.constructor.name === 'Headers';
=>const isHeaders = (headers) => headers.constructor?.name === 'Headers';

Currently index.ts is being used as types in package.json which is causing compiler errors when upgrading to newer versions of typescript (since it tries to compile the entire package instead of just referencing the types). I think this could be resolved by generating an index.d.ts and referencing that instead.

Not working in IE11 becuase In library you are using node-fetch module which does not work in ie11 so please include
require('es6-promise').polyfill();
require('isomorphic-fetch');

top of your code.

Cause of issue: inside node-fetch

var getGlobal = function () {
// the only reliable means to get the global object is
// Function('return this')()
// However, this causes CSP violations in Chrome apps.
if (typeof self !== 'undefined') { console.log('self', self.fetch); return self; }
if (typeof window !== 'undefined') { console.log('window'); return window; }
if (typeof global !== 'undefined') { return global; }
throw new Error('unable to locate global object');
}

var global = getGlobal();
console.log('global', global);
module.exports = exports = global.fetch;

exports.default = global.fetch.bind(global); this line throw exception becuase fetch is undefined in ie11

The devDependency ava was updated from 2.1.0 to 2.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ava is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hello,

I had initiate a new project with Angular, and install the following packages:

• angular-apollo
• apollo-upload-client
• @lifeomic/axios-fetch
• axios

to test onUploadProgress but I get the following error:

./node_modules/@lifeomic/axios-fetch/src/typeUtils.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: <PATH\node_modules\@lifeomic\axios-fetch\src\typeUtils.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.

I think the problem is the tsconfig.json file.

Best regards

After the latest update, the following error occurs when attempting to import the library into a strict TypeScript project.

node_modules/@lifeomic/axios-fetch/src/index.ts:71:3 - error TS2322: Type '(input?: string | undefined, init?: FetchInit | undefined) => Promise<Response>' is not assignable to type 'AxiosFetch'.
  Type 'Promise<Response>' is missing the following properties from type 'Response': clone, headers, ok, redirected, and 14 more.

71   return axiosFetch.bind(undefined, axios, transformer);

This appears to be because the .ts files are being published along side the .js files rather than simple .d.ts declarations.

Recommendation, have tsc output to a dist folder and publish that with a declared types in your package.json.

Another Recommendation, attempt to compile in strict mode and fix the type errors to reduce potential bugs.

In Node.js 18, an experimental global fetch API is available by default (https://nodejs.dev/en/blog/announcements/v18-release-announce#fetch-experimental). axios-fetch currently assumes node-fetch as the underlying fetch mechanism.

This has compatibility issues in Node v18's fetch implementation for handling of 204 no-content results.

Nodes fetch (backed by undici) expects a 204 response to have a nullable body, however axios-fetch returns an empty buffer, resulting in the following error

TypeError {
    message: 'Response constructor: Invalid response status code 204',
}

The expectation is that axios-fetch also returns a nullable body for 204 no-content responses.

The current workaround to this is to avoid utilising nodes fetch impl via --no-experimental-fetch or override our global references with node-fetch

The dependency form-data was updated from 2.4.0 to 2.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

form-data is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

The version of node-fetch used for your tests has a vulnerability: https://ossindex.sonatype.org/vulnerability/CVE-2022-0235?component-type=npm&component-name=node-fetch&utm_source=auditjs&utm_medium=integration&utm_content=4.0.37
This issue has been fixed in the 3.x branch of node-fetch.

Could you please update your dependency so that this vulnerability is not carried over in other projects?

Thanks in advance.

Per fetch's spec it should also accept as "input" a Request object which current implementation does not support.

Cookies without this module are passed to requests, I tried creating an instance of axios with the withCredentials option, the cookies will get passed.

How are cookies passed?

Hello,
Thank you for the library, it is very useful.
I encountered a problem I didn't have before, I unfortunately do not remember the last version of axios it worked with.
basically, I am using this library to with my own axios instance and urql to fetch datafrom a graphql server without having to configure urql for csrf.
I updated my dependencies to the latest versions today and tried to make some request but they all fail with an incorrect csrf token error.
Checking the request headers showed that the X-XSRF-TOKEN header is not set for graphql post request, but normal axios request automatically set the header.
I tried setting up an interceptor on the axios instance to log the config, but it also only works when making regular axios request.

Axios

import { boot } from 'quasar/wrappers';
import Axios, { AxiosInstance } from 'axios';

declare module '@vue/runtime-core' {
  interface ComponentCustomProperties {
    $axios: AxiosInstance;
  }
}

const axios = Axios.create();
axios.defaults.withCredentials = true;
axios.interceptors.request.use(
  (config) => {
    console.log('config: ', config);
    return config;
  },
  (error) => {
    return Promise.reject(error);
  }
);

export default boot(async ({ app }) => {
  await axios.get(`${process.env.API_URL}/auth/csrf-token`);
  app.config.globalProperties.$axios = axios;
});

export { axios };

urql

import { createClient as createWSClient } from 'graphql-ws';
import { buildAxiosFetch } from '@lifeomic/axios-fetch';
import axios from 'axios';
import { authExchange } from '@urql/exchange-auth';
import { AuthState } from 'src/interfaces';
import { useJwt } from '@vueuse/integrations/useJwt';

const getAuth = async () => {
  const token = localStorage.getItem('token');
  if (!token) {
    return token ? { token } : null;
  }
  const result = await axios.get<string>(
    `${process.env.API_URL}/auth/refresh-token`
  );
  if (result.data) {
    localStorage.setItem('token', result.data);
    return {
      token: result.data,
    };
  }
  localStorage.clear();
  //logout logic here
  return null;
};

const wsClient = createWSClient({
  url: `${process.env.API_WS_URL}/graphql`,
  connectionParams: async () => ({
    authToken: (await getAuth())?.token,
  }),
});

const client = createClient({
  fetch: buildAxiosFetch(axios),
  url: `${process.env.API_URL}/graphql`,
  requestPolicy: 'cache-and-network',
  exchanges: [
    dedupExchange,
    cacheExchange,
    authExchange({
      addAuthToOperation: ({ authState, operation }) => {
        const state = authState as AuthState;
        if (!state || !state.token) {
          return operation;
        }
        const fetchOptions =
          typeof operation.context.fetchOptions === 'function'
            ? operation.context.fetchOptions()
            : operation.context.fetchOptions || {};
        return makeOperation(operation.kind, operation, {
          ...operation.context,
          fetchOptions: {
            ...fetchOptions,
            headers: {
              ...fetchOptions.headers,
              Authorization: `Bearer ${state.token}`,
            },
          },
        });
      },
      willAuthError: ({ authState }) => {
        const state = authState as AuthState;
        if (!state || !state.token) return true;
        const { payload } = useJwt(state.token);
        if (payload.value && payload.value.exp) {
          const isTokenExpired = payload.value.exp * 1000 < Date.now();
          return isTokenExpired;
        }
        return !!payload;
      },
      didAuthError: ({ error }) => {
        return error.graphQLErrors.some(
          (err) => err.extensions?.code === 'FORBIDDEN'
        );
      },
      getAuth,
    }),
    multipartFetchExchange,
    subscriptionExchange({
      forwardSubscription(operation) {
        return {
          subscribe: (sink) => {
            const dispose = wsClient.subscribe(operation, sink);
            return {
              unsubscribe: dispose,
            };
          },
        };
      },
    }),
  ],
});

export default boot(({ app }) => {
  app.use(UrqlPlugin, client);
});

axios: v0.26
@lifeomic/axios-fetch: v3.0.0
@urql/vue: v0.6.1

I'm using this package as a fetch implementation for the Apollo Client in Gatsby. I want to upload files to the server, so I'm using the package: apollo-upload-client. But when inspecting the payload that gets sent, it says:

[object FormData], instead of serializing everything.

Any suggestions on how to fix this?

Hello guys, hope you are well!
First of, thanks for developing this awesome library, much appreciated! ❤️

I'm trying to import useAxiosFetch in my React app as an ES6 module:
import { useAxiosFetch } from '@lifeomic/axios-fetch'

Unfortunately, I'm getting the following error:

fromRequireContextWithGlobalFallback.js:21 ReferenceError: exports is not defined
    at Module../node_modules/@lifeomic/axios-fetch/src/index.js (index.js:15)

Lines causing error:

Object.defineProperty(exports, "__esModule", {
  value: true
});

Could you please let me know what could be the cause of it?

I'm using v2.0 with Webpack. Let me know if you need me to provide any additional details.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Currently, the library solely depends on node-fetch for providing fetch primitives like Header class and so on.

We plan to use it in the browser context, where these primitives are provided by the runtime and we would like to avoid packing node-fetch because of it. I would like to provide a similar abstraction that https://github.com/sindresorhus/ky-universal uses for NodeJS and browser, utilizing the browser property in package.json.

Hi! I'm running into an issue where, if someone attempts a request while they are offline, result.headers on line 40 blows up because err.response is undefined. I'm unsure of the proper way to go about fixing this, or if there is something I should be doing with the axios instance before passing it to axios-fetch to avoid this issue altogether.

Any help would be greatly appreciated!

Hello,

I am using axios fetch with @urql/vue to fetch data but it causes characters (french, japanese) to be incorrectly displayed.
The following is the code I use.

import { boot } from 'quasar/wrappers';
import urql, {
  createClient as createUrqlClient,
  dedupExchange,
  makeOperation,
  Exchange,
} from '@urql/vue';
import { cacheExchange } from '@urql/exchange-graphcache';

import { multipartFetchExchange } from '@urql/exchange-multipart-fetch';
import { buildAxiosFetch } from '@lifeomic/axios-fetch';
import Axios from 'axios';

import { devtoolsExchange } from '@urql/devtools';

export default boot(async ({ app }) => {
  const axios = Axios.create({
    baseURL: `${process.env.API_URL}`,
  });
  axios.defaults.withCredentials = true;

  const exchanges: Exchange[] = [
    devtoolsExchange,
    dedupExchange,
    cacheExchange({}),

    multipartFetchExchange,
  ];

  const client = createUrqlClient({
    fetch: buildAxiosFetch(axios) as unknown as typeof fetch,
    url: `${process.env.API_URL}/graphql`,
    requestPolicy: 'cache-and-network',
    exchanges,
  });
  app.use(urql, client);
});

I tried with axios only and also urql without axios-fetch and they both display characters correctly.

I can't use axios-fetch with together with https://github.com/Flyrell/axios-auth-refresh, because the errors seem to get thrown in a way that cannot be intercepted.

For example,

const refreshAuthLogic = (failedRequest: any): Promise<any> => {
...
}

createAuthRefreshInterceptor(axios, refreshAuthLogic, { skipWhileRefreshing: false });

const httpLink = createHttpLink({
  uri: '/backend/graphql/',
  fetch: buildAxiosFetch(axios),
});

This works for requests done through axios, but not for apollo requests. The errors that get thrown can't get intercepted by refreshAuthLogic.