- @zachdaniel.dev is there a way to not have igniter install itself as a dependency when running e.g. `mix igniter.install`? I only want to use the igniter version installed globally, not add it to the project.
- mix igniter.install works if you just have the archive but igniter isn't a part of the project, but it also adds itself as a dependency. You could remove igniter after, and we could potentially automate that. There are benefits to having it as a dependency though. Why don't you want the dep?May 8, 2025 10:33
- Yep, I removed it manually after now. It'd be nice if adding Igniter was optional. I don't want to force it on my fellow devs or onto the project just to install a mix package :D
- It's a dev/test dependency so it doesn't go to prod, and increasingly there are projects who's `mix gen.*` tasks rely on igniter etc. I've considered making it so that if you install into a project that doesn't have it that it removes itself automatically, but we can't guarantee the installed
- package doesn't rely on igniter in some way (like for its mix tasks). We can potentially add a `--remove` flag to make that opt in.
- That’d be great. I really only use igniter for adding packages and removing igniter after every call is a bit tedious. But yeah, I might not be the best user to ask for this but I’d be in favor of an optional igniter addition