blocks|key|4412663|text|当你写这个时：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4412664|mix+deps.get+--only+prod|offset|length|style|CODE|4412665|它将获取prod环境的所有依赖项，即没有only选项的依赖项，以及指定了only选项并包含:prod+(例如{:some_dep,+"~>+0.8",+only:+[:prod]})的依赖项。|4412666|4412667|defp+deps+do
++[
++++{:some_dep,+"~>+0.8"}
++]
end|code-block|syntax|javascript|4412668|这告诉mix在中安装任何运行的环境。|BOLD|4412669|4412670|defp+deps+do
++[
++++{:another_dep,+"~>+0.8",+only:+[:dev]}
++]
end|4412671|它告诉mix只在您的环境是dev+(MIX_ENV=dev)时才安装MIX_ENV=dev。如果您在任何其他环境(例如prod)中，mix+deps.get只会忽略another_dep而不会安装它。|4412672|写这篇文章：|4412673|def+project+do
++[
++++#+...
++++deps:+deps(Mix.env()),
++]
end|4412674|将导致**+(CompileError)+mix.exs:13:+undefined+function+deps/1，因为在您的mix.exs中，只定义了deps/0。现在你可以告诉我为什么不实现deps(:dev)，deps(:prod)等等.好吧，如果您阅读我前面解释过的内容，您会发现这是没有意义的，因为每个环境的dep分离都已经得到了处理:)|4412675|entityMap^0|0|0|O|0|K|4|10|4|19|5|1I|10|0|0|0|7|8|0|0|0|D|3|I|B|Y|B|1U|C|2A|B|0|0|0|3|1J|1S|7|25|6|2Q|A|31|B|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]|$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|J|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1J|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|1K|8|@$D|1L|E|1M|F|R]]|9|@]|A|$]]|$1|S|3|4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|T|3|U|5|M|7|1O|8|@]|9|@]|A|$N|O]]|$1|V|3|W|5|6|7|1P|8|@$D|1Q|E|1R|F|G]|$D|1S|E|1T|F|G]|$D|1U|E|1V|F|G]|$D|1W|E|1X|F|G]|$D|1Y|E|1Z|F|G]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|20|8|@]|9|@]|A|$]]|$1|Z|3|10|5|M|7|21|8|@]|9|@]|A|$N|O]]|$1|11|3|12|5|6|7|22|8|@$D|23|E|24|F|G]|$D|25|E|26|F|G]|$D|27|E|28|F|G]|$D|29|E|2A|F|G]|$D|2B|E|2C|F|G]]|9|@]|A|$]]|$1|13|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]]|14|$]]

When you write this :

<code>mix deps.get --only prod</code>

It will fetch all dependencies for the prod environment, namely the dependencies where there is no <code>only</code> option, and dependencies where the <code>only</code> option is specified and containing <code>:prod</code> (e.g <code>{:some_dep, "~&gt; 0.8", only: [:prod]}</code>)

When you write this :

<pre><code>defp deps do
 [
 {:some_dep, "~&gt; 0.8"}
 ]
end
</code></pre>

That tells mix to install <code>some_dep</code> in any environment it is run into.

When you write this :

<pre><code>defp deps do
 [
 {:another_dep, "~&gt; 0.8", only: [:dev]}
 ]
end
</code></pre>

It tells mix to install <code>another_dep</code> only when your environment is <code>dev</code> (<code>MIX_ENV=dev</code>).
If you are in any other environment (e.g. prod), <code>mix deps.get</code> will simply ignore <code>another_dep</code> and won't install it.

writing this :

<pre><code>def project do
 [
 # ...
 deps: deps(Mix.env()),
 ]
end
</code></pre>

will result in <code>** (CompileError) mix.exs:13: undefined function deps/1</code> because in your <code>mix.exs</code>, only <code>deps/0</code> is defined. Now you might tell me why not implement <code>deps(:dev)</code>, <code>deps(:prod)</code> and so on... Well, if you read what I explained before, you'll see that it is pointless, since the deps separation for each environment is already taken care of :)

blocks|key|4412727|text|我要用相反的顺序来解决这些问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4412728|如果在多个环境中使用依赖项，则使用deps(Mix.env)将强制您多次指定每个依赖项。与…有关的东西|offset|length|style|CODE|4412729|def+deps(:dev)+do
++[
++++{:ecto,+"~>+2.1"}
++++{:credo,+"~>+0.8",+runtime:+false}
++]
end
def+deps(:test)+do
++[
++++{:ecto,+"~>+2.1"}
++]
end|code-block|syntax|javascript|4412730|我承认，我甚至不知道这是否有效，但是如果您只指定了:only选项，那么已经为您处理的内容添加了太多的代码。|4412731|使用:only可以指定应该在哪些环境中使用依赖项。在您的示例中，{:credo,+"~>+0.8",+only:+[:dev],+runtime:+false}告诉mix只应该在dev环境中使用credo包。如果不包括:only选项，则包将在所有环境中使用。|4412732|$+mix+deps.get+--only+prod只检索与生产环境相关的包。从前面的示例中，credo包将不会被检索，因为您告诉mix只应该在dev环境中使用credo。|4412733|entityMap^0|0|H|D|0|0|P|5|0|2|5|W|1C|31|5|0|0|Q|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@$D|13|E|14|F|G]|$D|15|E|16|F|G]|$D|17|E|18|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$]]

I'm going to address these in reverse order.

using <code>deps(Mix.env)</code> would force you to specify each of your dependencies multiple times if they are used across multiple environments. Something along the lines of

<pre><code>def deps(:dev) do
 [
 {:ecto, "~&gt; 2.1"}
 {:credo, "~&gt; 0.8", runtime: false}
 ]
end
def deps(:test) do
 [
 {:ecto, "~&gt; 2.1"}
 ]
end
</code></pre>

I will admit that I do not even know if this would work, but this is adding too much code for something that is already handled for you if you just specify the <code>:only</code> option.

Using <code>:only</code> allows you to specify which environments a dependency should be used in. In your example, <code>{:credo, "~&gt; 0.8", only: [:dev], runtime: false}</code> you are telling mix that the credo package should only be used in the dev environment. If you do not include the <code>:only</code> option, the package will be used in all environments.

<code>$ mix deps.get --only prod</code> will only retrieve the packages relevant to the production environment. From the previous example, the credo package will not be retrieved because you told mix that credo should only be used in the dev environment.

There are multiple ways to install Elixir dependencies. I wonder what happens in the following cases:

<h3>1.</h3>

<pre><code>mix deps.get --only prod
</code></pre>

What exactly dependencies are being fetched then?

<h3>2.</h3>

<pre><code>defp deps do
 [
 {:credo, "~&gt; 0.8", only: ~w(dev)a, runtime: false},
 ]
end
</code></pre>

How <code>only</code> option impact on a particular dependency?

<h3>3.</h3>

<pre><code>def project do
 [
 # ...
 deps: deps(Mix.env()),
 ]
end
</code></pre>

What is the difference if we specify dependencies like that?

<hr>

I'm confused a little bit when to use what regarding defining dependencies.

How to fetch Elixir dependencies per environment?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

安装Elixir依赖项有多种方法。我想知道在下列情况下会发生什么情况：1.mix deps.get --only prod那么，究竟获取了哪些依赖项呢？2.defp deps do  [    {:credo, "~> 0.8", only: ~w(dev)a, runtime: false},  ]endonly选项...

问如何在每个环境中获取Elixir依赖项？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在每个环境中获取Elixir依赖项？EN