-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: initial release #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Snapshots match the ones from the rollup plugin, though with a different format since we use the native runner instead of tap.
Cool. Great stuff. Though; The Eik Rollup plugin is a small abstraction on top of a generic import mapping plugin. So this is an abstraction on top of another abstraction. The Eik Rollup plugin is pretty small and I wonder if its worth duplicating the Eik Rollup plugin in here with the additional Vite stuff just to avoid the abstraction on top of an abstraction layers. Thoughts? |
I think it's fine going via the Rollup plugin as long as Vite uses Rollup under the hood. |
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Goal is to make using Eik with Vite slightly more ergonomic than with the Rollup plugin.
Similar to viteik, but less opinionated in the output department.