Vite – Next Generation Front End Tooling

Re:Vite – Next Generation Front End Tooling by boredtofears on Sunday July 03, 2022 @02:09PM (#31969707)

I dunno if it's just me, but I've always found live reload to be an overstated benefit. I usually have a mental model of what I'm trying to code that I don't want to check until it's at a specific state - the seconds it takes to press reload doesn't really add up to that much.

I'd say it's more beneficial for CSS styling but I usually mock up my changes in the dev inspector and then copy it over anyways.

[ Parent | on HN ]

Re:Vite – Next Generation Front End Tooling by aidos on Sunday July 03, 2022 @02:24PM (#31969826)

Exactly that though. For a SPA you’re going to have a bunch of state loaded and you don’t want to refresh. If you’re using something like tailwind where you’re transpiling your css too then it’s a major boon to have it hot reloaded.

I’ve found vite to be an awesome dev experience.

[ Parent | on HN ]

Re:Vite – Next Generation Front End Tooling by drschwabe on Sunday July 03, 2022 @09:55PM (#31972729)

Not just you.

Hotreload can be handy to some extent, annoying in others - I like to preserve state of given app including what the dom looks like + the window/memory state in devtools. Iterate in code, refresh, then compare. You can do that with multiple browser tabs for example. But not with hotreloading; each tab will re-render/reload the global window state.

[ Parent | on HN ]