Internal: we don't need to explicitly say that the migration code itself was in zipper.dev codebase. It's way more cool hiding this fact :P
The below is just an outline.
How we used Zipper to migrate Zipper
Problem: all Typescript files were .ts but being treated as .tsx, we the user to control if they want .ts or .tsxSolution: move all filenames to .tsx, update imports using a codemod tool
Of course, the solution looks a lot like a script. And Zipper provide an excellent set of tooling to play around with scripts.
We did a pair programming session on Zipper to create the script to run the migration, ran it, and saw in real time our own migration script being updated to .tsx with all the imports fixed
dopamine kick F**k yea moment
We're happy to say that you can do this if you want too. Zipper has support for database connectors: bring your data, write the script, lets us handle the rest.
Internal: we don't need to explicitly say that the migration code itself was in zipper.dev codebase. It's way more cool hiding this fact :P
The below is just an outline.
How we used Zipper to migrate Zipper
Problem: all Typescript files were
.tsbut being treated as.tsx, we the user to control if they want.tsor.tsxSolution: move all filenames to.tsx, update imports using a codemod toolOf course, the solution looks a lot like a script. And Zipper provide an excellent set of tooling to play around with scripts.
We did a pair programming session on Zipper to create the script to run the migration, ran it, and saw in real time our own migration script being updated to
.tsxwith all the imports fixedWe're happy to say that you can do this if you want too. Zipper has support for database connectors: bring your data, write the script, lets us handle the rest.