mix deps.sync

[Neil Lyons]

I removed a dependency from `deps/0` in  `mix.exs` and realised that it didn't remove it from the lock file.

Is `mix deps.clean --unlock --unused` the correct way to fully remove a dependency [0]?

If so I was thinking most developers probably don't realise this. Perhaps a new alias could be added called `deps.sync` that you run after adding/removing dependencies 🤔

eg.

"deps.sync": ["deps.get", "mix deps.clean --unlock --unused"]

[0]: https://til.hashrocket.com/posts/biytzjjppd-how-to-remove-unused-deps-from-mixlock

[Jonathan Arnett]

I fully agree that this needs to be more discoverable.  Every year or so, I remove a dependency and then have to go find that TIL article that gives me the right flags.

[José Valim]

"mix deps.unlock --unused" is generally the way to go about it. You can also add "mix deps.unlock --check-unused" to CI.

--
You received this message because you are subscribed to the Google Groups "elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/35b1b446-ed20-46d6-ae82-56ea08bb352bn%40googlegroups.com.