awesome-vite VS vite-tsconfig-paths

Vite is a modern front-end build tool that significantly improves the development experience with its fast cold server start and hot module replacement. It leverages native ES modules and is optimized for speed and efficiency.

🔨 Vite ⚡

https://github.com/vitejs/awesome-vite#react

I suggest Vite community templates https://github.com/vitejs/awesome-vite

here

I saw Vite but not sure how easy it is to switch to that from an existing project.

I think most around here currently recommend Vite for a quick up and running SPA. If you'd like some tooling already set up, you can check out some of the community made templates at awesome vite.

It is super easy to get started with Vite and there is really no hard learning curve either. If you want to learn more about all the awesome things Vite can do, Check out this repo.

Vite has templates and plugins that you can install as project dependencies or use them. You can find a list of that and more here.

Following suggestion in the issue, i looked at vite-tsconfig-paths which is even better because i already have configured vscode through typescript config:

Try this one. https://github.com/aleclarson/vite-tsconfig-paths

We need vite-tsconfig-paths in order to tell Vite how to resolve absolute paths from the tsconfig file. This way you can import modules like this:

You can use vite-tsconfig-paths on SvelteKit project. And it doesn't work, plese try delete generated folder for dev server like .svelte-kit.

We already have configured path aliases with webpack and tsconfig - so I wanted to keep that behavior. Luckily we have the vite-tsconfig-paths exactly for that. It worked well. I could also try using the alias for that.