Consider retiring in favor of vite, or mentioning vite in README

[rfay]

It seems like vite has taken over the world and left browsersync behind.

We could

• Mark this as lightly maintained
• Mention vite and related add-ons in README

Related:

• docs: Migrate Vite Setup documentation into DDEV docs ddev#7466

[jakeparis]

I can only speak for my own use, but this addon really doesn't serve the same purpose as vite at all (unless there's some ways of using vite that I haven't come across). When I use this add on, it's generally to watch single css files that are not compiled, and are part of a wordpress plugin that has no compile step at all. It's just a good old fashioned way to not have to wear out the F5 key on my keyboard.

I've only ever come across vite in settings that involve either a SPA, or at least a javascript entry point with config files, etc.

Having said that, I'll admit that I tend not to reach for this addon in projects, since with more complicated wordpress setups, it doesn't always work correctly and I haven't been able to (or haven't put the time in to) figure out why.

[tyler36]

This addon works great for projects that don't need an asset bundler and iterating simple demos.
I find myself working less on these type of projects.