maglev-core icon indicating copy to clipboard operation
maglev-core copied to clipboard

Installation is impossible, if not using Yarn or NPM

Open henrikbjorn opened this issue 10 months ago • 5 comments

Trying to add Maglev to a site that is already using vite_rails seems to be impossible without jumping through a huge amounts of hoops.

It seems that Maglev is instantiating its own ViteRuby instance instead of using the singleton already available ViteRuby.instance and then forces the usage of yarn or npx.

Is there a reason for not "just" having a dependency added to package.json and using the normal flow for handling npm dependencies?

Also is there a reason for the "engine" custom vite configuration, instead of helping the user to configure their current setup?

henrikbjorn avatar Dec 27 '24 09:12 henrikbjorn