My Type of Library: Axios TypeScript Conversion

1

axios

This is the first post in an ad-hoc series where I convert libraries to TypeScript, and analyze the results. In the same vein as my re-conversion of the Turbo Framework to TypeScript, I decided to take a popular JavaScript library, this time one that had always been in JavaScript, and see what converting the codebase to TypeScript revealed. I chose Axios, because it’s:.

#Javascript UI Libraries #Developer Tools #JS Library 116 social mentions

2

Windsurf Editor

The functional issues revealed during the conversion show the flexibility of JavaScript and the clever “tricks” we often perform with it. In highlighting the issues, I utilized AI agents through the Windsurf editor, and when it offered suggestions for fixes, I realized that even with the extensive context provided by the codebase, its solutions were still sub-par and illustrative of the limits of how AI can help with TypeScript problems.

#Code Editor #Programming Tools #Developer Tools 12 social mentions

3

Claude AI

To that end, I’ll highlight some of the issues found in the conversion that necessitate functional changes, referencing both my converted code and the Axios main branch as of this writing. I’ll also compare the solutions to these issues that were provided by Claude 3.7, and contrast them with my preferred solutions to show how Claude conceives of the code and solutions, and how this differs from the way a skilled developer (if I do say so myself) views them.

#Ios #Writing Tools #Mac 76 social mentions