# What We Learned Migrating From Webpack to Vite

DevFeed: [What We Learned Migrating From Webpack to Vite](<https://devfeed.tech/articles/what-we-learned-migrating-from-webpack-to-vite-5290.md>)

Original publisher: [Read original article](<https://neon.com/blog/from-webpack-to-vite>)

Author: Roman Zaynetdinov

Published: 2024-11-20T17:59:21Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [Web Development](<https://devfeed.tech/topics/web-development.md>), [web applications](<https://devfeed.tech/topics/web-applications.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [go](<https://devfeed.tech/tags/go.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [migration](<https://devfeed.tech/tags/migration.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

## AI overview

Neon describes migrating its SPA build system from Webpack to Vite. The migration targeted faster builds, hot module replacement, fewer dependencies, and integration with a Go backend that renders HTML and injects user properties.

## Source excerpt

The Neon Console is a Single Page Application (SPA), or rather, a collection of SPAs. Static assets like JavaScript and CSS are served through CloudFront, while the HTML is dynamically rendered by our Go backend. In this post, we'll dive into our journey of migrating from webpack...