rebar3_hex
rebar3_hex copied to clipboard
erlef
Rebar3 Hex library
I am running latest rebar3 ``` rebar3 --version rebar 3.18.0 on Erlang/OTP 24 Erts 12.2 ``` And trying to upgrade the plugin `rebar3_hex` : ``` ➜ more ~/.config/rebar3/rebar.config {plugins, [rebar3_hex,...
In the case of a dry run, there's no need to prompt for a password what so ever. This could be solved a few ways. 1. If the dry run...
I had the proper `rebar.config` setup: ```erlang {docs, [{edoc_opts, [{preprocess, true}, {doclet, edoc_doclet_chunks}, {layout, edoc_layout_chunks}, {dir, "_build/default/lib/telemetry/doc"}]} ``` however I kept getting this error: ``` % rebar3 hex docs ===>...
Currently we have on rebar3.org docs around `config` commands. This has not been implemented yet. The config command should mirror mix hex as far as UX goes and should serve...
Support for `optional_applications` will be merged into OTP soon: https://github.com/erlang/otp/pull/2675 This plugin should support it by checking `optional_applications` and marking any dependency that is found in that list as optional...
We should add an audit provider ala [mix hex.audit](https://hexdocs.pm/hex/Mix.Tasks.Hex.Audit.html). Said provider merely shows all dependencies in the users application that have been marked as retired.
One thing missing from this project is a doc that goes over how you can go about adding a feature, fixing a bug, etc. and what's more adequately testing it...
In order to provide a consistent experience we should consider vendoring in hex_core. This specifically helps mitigate against stale cases where by a user has upgraded rebar3_hex but for some...
Currrently, the shape of errors is non standard. In some providers a function may match on `{error, Reason}` and return raise `Reason`, others may return raise with the entire tuple....
We should add an info provider ala [mix hex.info](https://hexdocs.pm/hex/Mix.Tasks.Hex.Info.html). Said provider merely fetches and prints information about a specific package and version.