Are there any Migration Guide for v1.0.0?

[ghiscoding]

I'm really excited about this new version 1.0.0 that just came out but I cannot find any Migration Guide anywhere. All I could find is the following in the changelog

There are multiple deprecations, refactors and fixes provided in this release. Please read through the full release notes to see how this may impact your project and use case.

But that is not very helpful, I don't wish to have to go through every single PR that came out to find what needs to change. Are there any Migration Guide here or over the internet that can be helpful?

Thanks for the new version

[jasonsaayman]

I will be adding one as soon as possible.

[amirhamdy]

any update on this would be really appreciated.

[brandonlenz]

Agree, a migration guide would be awesome. Is there at least a list of the breaking changes so that consumers will know what to look out for, and gauge the degree to which we might be affected?

e.g. the 1.0.0 tag does not list which changes are breaking

[PreisM]

Guide would be great, any update on this?

[MaximeAnsquer]

Hello, an upgrade guide would be very useful for me too. Thanks in advance!

[TomasTarasovic]

It has been over a year, is there any update about the upgrade guide? Thanks!

[LucasNovaes2016]

It would be really hepful if there was a migration guide.

[lODIN007l]

I think little by little they are considering making the guide

[jasonsaayman]

Yeah I will get to finishing it off, sorry been a busy time for me with IRL work

[amirhamdy]

any updates on this?

[baraeb92]

Most likely landing after a new year, I supposed.

It's the holiday season, so the maintainer understandably needed to take some time away from their primary job and their open-source project

[tmcdos]

[plourenco]

Is there any gain from comments like this? I've just subscribed to this thread to get feedback about the states of the migration guide. But these kind of comments don't speed up things, they just spam people...

[ames20]

I had issues upgrading as well - any progress on the guide?

[cburkins]

Agree with others, having a few bullet points on common errors during migration to v1.0 would be better than waiting for a perfect migration guide.

[miguelpinia]

I agree with this; it would be useful to keep updated our applications. Meanwhile, I won't touch anything related to axios.

[ghiscoding]

hey guys, so I'm the one who opened this discussion but since I'm still getting a lot of notifications that a migration guide is needed... We did the move a few months ago and it was actually pretty easy to do the migration. Our project uses Vue 3 and Vite, so prior to Axios 1.x being released, we were using @bundled-es-modules/axios to get Axios 0.x working as ESM in Vite, and the migration from that temp lib to the new Axios 1.x was quite simple

- import { axios } from '@bundled-es-modules/axios';
+ import axios from 'axios';

the only other issue we had was with the AxiosRequestConfig interface that we use in our http interceptors and for that we simply had to switch to the InternalAxiosRequestConfig interface

- import { axios, AxiosRequestConfig, AxiosResponse } from '@bundled-es-modules/axios';
+ import axios, { AxiosError, AxiosResponse, InternalAxiosRequestConfig } from 'axios';

function startInterceptors() {
  axios.interceptors.request.use(onRequestFullfilled, onRequestResponseRejected);
  axios.interceptors.response.use(onResponseFullfilled, onRequestResponseRejected);
}

async function onRequestResponseRejected(reason: AxiosError<string>) {
-  const originalRequest = reason.config;
+  const originalRequest = reason.config as InternalAxiosRequestConfig;
   // ...
}

and that's about it... obviously this doesn't cover all use case, but it does cover the basic usage. So there's no need to wait for a perfect Migration Guide, just give a try ;)

Cheers and happy coding

[jasonsaayman]

Thanks, I really will still get this out, I know it's largely on me and I have started. I will look to put up what I have thus far this weekend and open for additions from the community

[vovkvlad]

jsut in case: I've opened a PR updating req_config.md adding new stuff that was added recently, and updating existing props that has been changed : axios/axios-docs#126

[jasonsaayman]

awesome thanks

[rago4]

Your solution saved me hours of work, thank you! 🙇‍♂️

[ericyd]

This might have been true in the past but I believe axios now supports either an object with serialize property or a function

axios/lib/core/Axios.js

Lines 61 to 70 in b3be365

	if (utils.isFunction(paramsSerializer)) {
	config.paramsSerializer = {
	serialize: paramsSerializer
	}
	} else {
	validator.assertOptions(paramsSerializer, {
	encode: validators.function,
	serialize: validators.function
	}, true);
	}

[rfgonzalezweb]

hi, is there any action required to migrate from 0.24.X -> 1.4.0 ?

I checked this guide but couldn't find any clear path.
https://github.com/axios/axios/blob/main/UPGRADE_GUIDE.md

thanks in advance

[leonbloy]

See also

https://github.com/bmuenzenmeyer/axios-1.0.0-migration-guide

https://github.com/bmuenzenmeyer/axios-1.0.0-migration-guide/issues

[MarwenLabidi]

any update on this ?
i had problem when i migrate axios from [0.27.2] to [1.0.0]
all the ws request return unauthorized status?

[tameroski]

Had a similar issue where all my requests were missing the "Cookie" header, resulting in an unauthorized status. Adding the withCredentials: true parameter to each request solved the problem.
Might also be a server configuration issue (see #5824), but didn't tried that.

[ac185422]

Hi, just curious if there is any update on the migration guide and if latest 1.x version (currently 1.6.7) is stable to upgrade from 0.28.0 to. I see the latest 0.x version has fixed vulnerabilities in 0.27.2 as well as backported some 1.x features however I see others have held out on going above 1.x due to issues listed above as well as another post in which I read some 1.x versions were not stable #5114 (comment). Any guidance on this would be greatly appreciated