On
the Erlang libraries page of the current guide, for the `crypto` module:
> The `:crypto` module is not part of the Erlang standard library, but is included with the Erlang distribution. This means you must list `:crypto` in your project’s applications list whenever you use it. To do this, edit your `mix.exs` file to include:
>
> ```
> def application do
> [extra_applications: [:crypto]]
> end
> ```
> `:crypto` is a part of and is distributed with Erlang/OTP ...
And that doesn't seem to contradict what's in the Getting Started guide.
But I'm confused as to why that module should be added to the `:extra_applications` key. I just tried running the example code from the guide in a 'scratchpad' project that has NO (explicit) Mix deps, and only `:logger` listed in `:extra_applications` and the code worked fine in `iex`. Does that code work because I'm running it on my 'dev' computer? Would NOT adding `:crypto` to `:extra_applications` present a problem were I to deploy that project's code to another computer?
Or is `crypto` now (somehow) part of "the Erlang standard library"?
I'm just curious! But, if the guide is now incorrect about this, I'd be happy to submit a PR with any suitable changes.