Discussion on "Vite or Webpack? Why not both?"

Kirill · 2022-12-05T06:56:55.576Z

Introduction If you are working on a complex web application that uses React and Webpack, you have probably thought about ditching Webpack completely more than once because of bugs and slowness. This tutorial will explain the easiest way to solve thi...

Great read! I started to use Vite a lot more lately alongside Next and both are so good for React projects.

Nice write up. First snag I've hit is jsx support in a react project. Does your project not use jsx?

My project is using jsx and tsx in all the places

Kirill Aizenberg oh okay.. it just seems the config you posted in the article is missing all of that. Would you mind updating the config snippet?

Why not just "Turbopack"?

Turbopack is a relatively new build tool compared to Vite, so I would not recommend using it in the near future. Also, there are no significant differences between the two of them, both of them very fast.

While migrating to vite there are many errors coming my way like file type must be jsx instead of js. But even after renaming it throws other hard to debug errors. Can you help?

Hi, yes, I would like to help. What is the best way to contact you? Thanks

Thanks a lot Kirill Aizenberg , you can reach me on twitter (@vivsh1999).

Now, this is something I'll love to try out!

So would Webpack still be in the codebase and could you safely remove it, once you've completely moved to Vite?

Hi, yes, at first, you can use both of them. If, after some time, you see there are no issues with Vite, you can remove Webpack altogether.

Okay, thanks Kirill Aizenberg

Discussion

Vite or Webpack? Why not both?

Responses(6)

Recent discussions

Search Hashnode

Vite or Webpack? Why not both?

Responses(6)

Recent discussions