Project still active?

[eric-nicular]

Is this repo still maintained/usable?

I tried using this with Quasar V2 to make my Axios calls compatible with service workers, but am having difficulty. All the rest of my frontend data is being saved, but not the Axios GET or POST requests. Any assistance would be much appreciated.

[KaKi87]

As the repo was updated only 28 hours after you submitted this issue, I would have said no, but considering there has been no response nor activity from the owner since then, it might be today.

Personally I'm studying the possibility of using this adapter (or finding another maintained fetch adapter) to use axios on Deno :

import axios from 'https://unpkg.com/axios@1.1.3/dist/esm/axios.min.js';
import axiosFetchAdapter from 'https://jspm.dev/@vespaiach/axios-fetch-adapter@0.3.1';
const client = axios.create({
    adapter: axiosFetchAdapter
});

@kuu12, @odroltd, @dmitriib-slash, if you're planning to maintain the project, would you please consider unifying your efforts and enabling issues ?

Thanks.

[crhistianramirez]

@KaKi87 were you able to find an alternative? This project seems dead and looking for one that is compatible with axios v1+

[KaKi87]

I did : https://github.com/haverstack/axios-fetch-adapter

It doesn't officially support v1.x though.

[crhistianramirez]

Thanks! I see that although I was actually able to get that package to work with v1.x. Looks like they are referencing some library helpers that are no longer exported in v1.x, more info here but you can modify your webpack config to pull from the node module files directly

Here's what it looks like in next.js

const path = require("path");

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config) => {
    config.resolve.alias = {
      ...config.resolve.alias,
      // Fix: Missing "./lib/helpers" specifier in "axios" package
      "axios/lib": path.resolve(__dirname, "./node_modules/axios/lib"),
    };

    return config;
  },
};

module.exports = nextConfig;

Then it was just a matter of ignoring the peer dependency warnings with npm install --legacy-peer-deps