vite VS semantic-release

There's an Nuxt plugin https://github.com/nuxt/vite - as Nuxt still is using Vue 2 it's some kind of a wrapper around the vite-vue-2 plugin. My personal experience is kinda "junky" to be honest - I added to a "new" Nuxt Project (under 1 week of starting) to see how much better it will make the dev experience. Well... yes, the generating time (client & server) went from ~ 30ish sec. to under 10s, which is more than awesome. BUT then when I open the client in the browser for the first time I had to wait additional ~30s more to load and spin up everything underneath (looking at a blank page the entire time). So in my experience it was kinda working, but didn't invest any time to check this as we had a pretty shitty deadline and this was the last thing I wanted to loose time on lol

I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.

Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.

When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.

To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.

If your projects ar made in javascript and related tools, I'd suggest you to check: semantic-release