With ex_doc 0.25.5 and earmark 1.4.16, the following errors occur:
On Elixir 1.11 earmark does not compile
On Elixir 1.12 earmark produces compiler warnings however neither remediation (1) or (3) appear to work. I have not yet added :eex as a dependency since that is built into Elixir and shouldn't be required?
These errors do not appear with earmark 1.4.14.
Configuration
mix.lock for ex_cldr_dates_times is as follows. The same issues appear in at least ex_cldr_dates_times and ex_cldr_calendars. Both of these have earmark 1.4.16 in the lockfile. ex_cldr has earmark 1.4.14 in its lock file and compilation produces no errors.
earmark
Compiling 13 files (.ex)
== Compilation error in file lib/earmark/transform.ex ==
** (SyntaxError) lib/earmark/transform.ex:134:1: invalid location for heredoc terminator, please escape token or move it to its own line: """
(elixir 1.11.4) lib/kernel/parallel_compiler.ex:314: anonymous fn/4 in Kernel.ParallelCompiler.spawn_workers/7
could not compile dependency :earmark, "mix compile" failed. You can recompile this dependency with "mix deps.compile earmark", update it with "mix deps.update earmark" or clean it with "mix deps.clean earmark"
I have tried adding :eex to :extra_applications and even adding it to :xref but these have no effect.
Compiling 13 files (.ex)
warning: EEx.eval_file/1 defined in application :eex is used by the current application but the current application does not depend on :eex. To fix this, you must do one of:
1. If :eex is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :eex is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :eex, you may optionally skip this warning by adding [xref: [exclude: [EEx]]] to your "def project" in mix.exs
lib/earmark/cli/implementation.ex:137: Earmark.Cli.Implementation._get_content/2
warning: EEx.eval_string/1 defined in application :eex is used by the current application but the current application does not depend on :eex. To fix this, you must do one of:
1. If :eex is part of Erlang/Elixir, you must include it under :extra_applications inside "def application" in your mix.exs
2. If :eex is a dependency, make sure it is listed under "def deps" in your mix.exs
3. In case you don't want to add a requirement to :eex, you may optionally skip this warning by adding [xref: [exclude: [EEx]]] to your "def project" in mix.exs
Found at 2 locations:
lib/earmark/cli/implementation.ex:127: Earmark.Cli.Implementation._process_input/2
lib/earmark/cli/implementation.ex:136: Earmark.Cli.Implementation._get_content/2
Summary
With
ex_doc 0.25.5
andearmark 1.4.16
, the following errors occur:earmark
does not compileearmark
produces compiler warnings however neither remediation (1) or (3) appear to work. I have not yet added:eex
as a dependency since that is built into Elixir and shouldn't be required?These errors do not appear with
earmark 1.4.14
.Configuration
mix.lock
for ex_cldr_dates_times is as follows. The same issues appear in at least ex_cldr_dates_times and ex_cldr_calendars. Both of these haveearmark 1.4.16
in the lockfile. ex_cldr hasearmark 1.4.14
in its lock file and compilation produces no errors.Elixir 1.11.4
Environment
Compile error
Elixir 1.12.2
Environment
Compile warning
I have tried adding
:eex
to:extra_applications
and even adding it to:xref
but these have no effect.