Change bundler from rollup to vite

[NicolasOmar]

Objective

Change the main bundler tool from rollup implementation to vite.

---

Description

After several failed attempts to update rollup plugin dependencies and checking that there are no solutions nowadays, I decided to review actual alternatives that will avoid this kind of situation in future releases and maintenance rounds.
The option I will review in this ticket is vite.

---

Tasks

• Study Vite's bundler mode implementation.
• Remove rollup's implementation.
• Change build script to execute vite's.
• Check that the new build script is working.
• Check that the new lint script is working.
• Check that the new test script is working.
• Check that the new storybook build script is working.
• Send this renewed method to the next minor version (v4.1.0).

[NicolasOmar]

• Original article, which I based to start working on the migration.
  • The first try on a clean and viable project worked without hassle.
  • Migrating the changes to reactive-bulma's project has been problematic due to a compatibility issue with vite-plugin-dts.
    • I will raise a ticket to the project's repo to get a solution or possible steps to solve it.
  • I will work on mounting the library in its current state (in my local), check if it works for the main scenarios, and proceed.

[NicolasOmar]

New findings to be added as gattered knowledge:

• A specific issue regarding vite implementation on the current project failed due to a vite-plugin-dts build error.
  • I found the solution on a vite-plugin-dts issue.
• Then, I had a problem with my storybook build script at the pipeline level (it worked locally).
  • The solution was to uninstall all storybook-related dependencies, run the npx storybook@latest init command on the project, and adjust its configurations to mine.
• Last but not least, my linter configuration started to break after I initiated this ticket. Appears to be a common issue that is being solved as I am writing this explanation.
  • The solution has been to update the related packages to v8.15.0 or above.

[receter]

The problem with ajv sounds familiar to me, I think I had the same problem at some point. How did you solve it? By installing ajv?

I had another problem a while back that I traced back to having legacy-peer-deps in my global npm configuration. I think the ajv problem might be related to that. Because with lecacy-peer-deps the peer dependencies have to be installed manually…

[receter]

Yes, I just tested it and this was because of --legacy-peer-deps which is also in your .npmrc. Do you still know why you need that?

[NicolasOmar]

Hi @receter, As you suggested, I deleted the .npmrc file and made a clean install on the repo, and it worked like a charm.
I will include this fix in my next version (around next week).

Thank you for the work and solution.