Many frameworks use Vite as their build tool and dev server. This means that they are identified as Vite by framework-info, however they don't get recognised as the specific framework unless they are also defined in here. The benefit of identifying the specifc framework is that we can set specific options such as the output dir and build command, which are sometimes changed fromt he default. It also ensures that our stats are accurate.
As well as adding the specific frameworks, I have added them as exclusions for Vite, so that users don't have duplicates detected.
A picture of a cute animal (not mandatory, but encouraged)
🎉 Thanks for submitting a pull request! 🎉
Summary
Many frameworks use Vite as their build tool and dev server. This means that they are identified as Vite by framework-info, however they don't get recognised as the specific framework unless they are also defined in here. The benefit of identifying the specifc framework is that we can set specific options such as the output dir and build command, which are sometimes changed fromt he default. It also ensures that our stats are accurate.
As well as adding the specific frameworks, I have added them as exclusions for Vite, so that users don't have duplicates detected.
A picture of a cute animal (not mandatory, but encouraged)