WHAT WE LEARNED MIGRATING FROM WEBPACK TO VITE

Summary from the TLDR Web Dev newsletter

Neon migrated from Webpack to Vite to get Hot Module Replacement (HMR) capabilities, simplify its configuration, and unify tooling, though build times initially remained unchanged. It developed a custom Vite proxy to integrate with its Go backend and faced challenges like slower dev cold starts, syntax errors, and dependency conflicts. However, in the end, the migration improved the developer experience with HMR, reduced dependencies, and streamlined its setup across apps, tests, and Storybook.