blocks|key|2991483|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991484|根据composer's+manual的说法：|ordered-list-item|offset|length|2991485|2991486|要求-开发(仅限根用户)|style|BOLD|2991487|列出开发此软件包或运行测试等所需的软件包。默认情况下会安装根软件包的开发要求。install或update都支持--no-dev选项，该选项可防止安装开发人员依赖项。|CODE|2991488|因此，运行composer+install还将下载开发依赖项。|2991489|，|2991490|，原因其实很简单。在为特定库做贡献时，您可能希望运行测试套件或其他开发工具(例如symfony)。但如果将此库安装到项目中，则可能不需要这些开发依赖项:并不是每个项目都需要测试运行程序。|2991491|2991492|entityMap|0|LINK|mutability|MUTABLE|url|https://getcomposer.org/doc/03-cli.md^0|0|2|H|0|0|0|0|C|0|13|7|1B|6|1K|8|0|5|G|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|12|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|13|7|@]|8|@$D|14|E|15|1|16]]|9|$]]|$1|F|3|-4|4|5|6|17|7|@]|8|@]|9|$]]|$1|G|3|H|4|5|6|18|7|@$D|19|E|1A|I|J]]|8|@]|9|$]]|$1|K|3|L|4|5|6|1B|7|@$D|1C|E|1D|I|M]|$D|1E|E|1F|I|M]|$D|1G|E|1H|I|M]]|8|@]|9|$]]|$1|N|3|O|4|5|6|1I|7|@$D|1J|E|1K|I|M]]|8|@]|9|$]]|$1|P|3|Q|4|5|6|1L|7|@]|8|@]|9|$]]|$1|R|3|S|4|C|6|1M|7|@]|8|@]|9|$]]|$1|T|3|-4|4|5|6|1N|7|@]|8|@]|9|$]]|$1|U|3|-4|4|5|6|1O|7|@]|8|@]|9|$]]]|V|$W|$4|X|Y|Z|9|$10|11]]]]

<ol>
<li>According to <a href="https://getcomposer.org/doc/03-cli.md" rel="noreferrer">composer's manual</a>:

<blockquote>
 require-dev (root-only)
 
 Lists packages required for developing this package, or running tests, etc. The dev requirements of the root package are installed by default. Both <code>install</code> or <code>update</code> support the <code>--no-dev</code> option that prevents dev dependencies from being installed.
</blockquote>

So running <code>composer install</code> will also download the development dependencies.</li>
<li>The reason is actually quite simple. When contributing to a specific library you may want to run test suites or other develop tools (e.g. symfony). But if you install this library to a project, those development dependencies may not be required: not every project requires a test runner.</li>
</ol>

blocks|key|172730|text|来自composer站点(足够清楚)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172731|172732|+require#|blockquote|172733|172734|列出此程序包所需的程序包。除非满足这些要求，否则将不会安装该软件包。|172735|require+dev(仅根目录的)#|172736|列出开发此软件包或运行测试等所需的软件包。默认情况下会安装根软件包的开发要求。install或update都支持--no-dev选项，该选项可防止安装开发依赖项。|172737|172738|使用Composer中的require-dev，您可以声明开发/测试项目所需的依赖项，但在生产中并不需要。当您上传项目到您的生产服务器(使用git)时，require-dev部件将被忽略。|offset|length|style|CODE|172739|也请检查author和this+post发布的这个答案。|172740|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/18520121/when-do-you-use-require-dev-what-are-common-dev-dependencies|1|http://seld.be/notes/composer-installing-require-dev-by-default^0|0|0|0|0|0|0|0|0|24|B|0|4|6|0|B|9|1|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|17|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1D|8|@$P|1E|Q|1F|R|S]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1G|8|@]|9|@$P|1H|Q|1I|1|1J]|$P|1K|Q|1L|1|1M]]|A|$]]|$1|V|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]|13|$5|Y|Z|10|A|$11|14]]]]

From the composer site (it's clear enough)

<blockquote>
 require#
 
 Lists packages required by this package. The package will not be
 installed unless those requirements can be met.
 
 require-dev (root-only)#
 
 Lists packages required for developing this package, or running tests,
 etc. The dev requirements of the root package are installed by
 default. Both install or update support the --no-dev option that
 prevents dev dependencies from being installed.
</blockquote>

Using require-dev in Composer you can declare the dependencies you need for development/testing the project but don't need in production. When you upload the project to your production server (using git) <code>require-dev</code> part would be ignored.

Also check this answer posted by the <a href="https://stackoverflow.com/questions/18520121/when-do-you-use-require-dev-what-are-common-dev-dependencies">author</a> and <a href="http://seld.be/notes/composer-installing-require-dev-by-default" rel="noreferrer">this post</a> as well.

blocks|key|2991586|text|不同的环境|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2991587|通常，软件将在不同的环境中运行：|2991588|2991589|development|unordered-list-item|offset|length|style|CODE|2991590|testing|2991591|staging|2991592|production|2991593|2991594|不同环境中的不同依赖关系|2991595|在composer.json的require部分中声明的依赖项通常是在中运行应用程序或包所需的依赖项|2991596|2991597|2991598|2991599|2991600|环境，而在require-dev部分中声明的依赖关系通常是|2991601|2991602|developing|2991603|2991604|2991605|环境。|2991606|例如，除了用于实际运行应用程序的包之外，可能还需要用于开发软件的包，例如：|2991607|2991608|friendsofphp/php-cs-fixer+(检测并修复编码风格issues)|2991609|squizlabs/php_codesniffer+)(检测并修复编码风格issues)|2991610|phpunit/phpunit+(使用tests)|2991611|etc.|2991612|驱动开发|2991613|部署|2991614|现在，在development和testing环境中，您通常会运行|2991615|$+composer+install|code-block|syntax|javascript|2991616|要安装production和development依赖项，请执行以下操作。|2991617|但是，在staging和production环境中，您只需要安装运行应用程序所需的依赖项，并且作为部署过程的一部分，您通常会运行|2991618|$+composer+install+--no-dev|2991619|仅安装production依赖项。|2991620|语义学|2991621|换句话说，|2991622|2991623|require|2991624|require-dev|2991625|2991626|在运行以下命令时指示composer应安装哪些包|2991627|$+composer+install|2991628|或|2991629|$+composer+install+--no-dev|2991630|这就是全部。|2991631|注意:永远不会安装应用程序或软件包所依赖的软件包的开发依赖项|BOLD|2991632|有关参考，请参阅：|2991633|2991634|https://getcomposer.org/doc/04-schema.md#require|2991635|https://getcomposer.org/doc/04-schema.md#require-dev|2991636|2991637|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|B|0|0|7|0|0|7|0|0|A|0|0|0|1|D|F|7|0|0|0|7|0|0|A|0|0|5|B|0|0|0|A|0|0|7|0|0|0|0|0|0|P|0|0|P|0|0|F|0|0|0|0|4|B|G|7|0|0|3|A|E|B|0|4|7|C|A|0|0|3|A|0|0|0|0|0|7|0|0|B|0|0|A|8|0|0|0|0|0|0|P|0|0|0|0|1C|0|0|0|1G|1|0|0^^$0|@$1|2|3|4|5|6|7|36|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|37|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|38|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|39|8|@$H|3A|I|3B|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|3C|8|@$H|3D|I|3E|J|K]]|9|@]|A|$]]|$1|N|3|O|5|G|7|3F|8|@$H|3G|I|3H|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|G|7|3I|8|@$H|3J|I|3K|J|K]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|3L|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|3M|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|3N|8|@$H|3O|I|3P|J|K]|$H|3Q|I|3R|J|K]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|3S|8|@]|9|@]|A|$]]|$1|X|3|O|5|G|7|3T|8|@$H|3U|I|3V|J|K]]|9|@]|A|$]]|$1|Y|3|Q|5|G|7|3W|8|@$H|3X|I|3Y|J|K]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|3Z|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|40|8|@$H|41|I|42|J|K]]|9|@]|A|$]]|$1|12|3|-4|5|6|7|43|8|@]|9|@]|A|$]]|$1|13|3|14|5|G|7|44|8|@$H|45|I|46|J|K]]|9|@]|A|$]]|$1|15|3|M|5|G|7|47|8|@$H|48|I|49|J|K]]|9|@]|A|$]]|$1|16|3|-4|5|6|7|4A|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|4B|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|4C|8|@]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|4D|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|G|7|4E|8|@$H|4F|I|4G|J|K]]|9|@]|A|$]]|$1|1E|3|1F|5|G|7|4H|8|@$H|4I|I|4J|J|K]]|9|@]|A|$]]|$1|1G|3|1H|5|G|7|4K|8|@$H|4L|I|4M|J|K]]|9|@]|A|$]]|$1|1I|3|1J|5|G|7|4N|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|4O|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|4P|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|4Q|8|@$H|4R|I|4S|J|K]|$H|4T|I|4U|J|K]]|9|@]|A|$]]|$1|1Q|3|1R|5|1S|7|4V|8|@]|9|@]|A|$1T|1U]]|$1|1V|3|1W|5|6|7|4W|8|@$H|4X|I|4Y|J|K]|$H|4Z|I|50|J|K]]|9|@]|A|$]]|$1|1X|3|1Y|5|6|7|51|8|@$H|52|I|53|J|K]|$H|54|I|55|J|K]]|9|@]|A|$]]|$1|1Z|3|20|5|1S|7|56|8|@]|9|@]|A|$1T|1U]]|$1|21|3|22|5|6|7|57|8|@$H|58|I|59|J|K]]|9|@]|A|$]]|$1|23|3|24|5|6|7|5A|8|@]|9|@]|A|$]]|$1|25|3|26|5|6|7|5B|8|@]|9|@]|A|$]]|$1|27|3|-4|5|6|7|5C|8|@]|9|@]|A|$]]|$1|28|3|29|5|G|7|5D|8|@$H|5E|I|5F|J|K]]|9|@]|A|$]]|$1|2A|3|2B|5|G|7|5G|8|@$H|5H|I|5I|J|K]]|9|@]|A|$]]|$1|2C|3|-4|5|6|7|5J|8|@]|9|@]|A|$]]|$1|2D|3|2E|5|6|7|5K|8|@$H|5L|I|5M|J|K]]|9|@]|A|$]]|$1|2F|3|2G|5|1S|7|5N|8|@]|9|@]|A|$1T|1U]]|$1|2H|3|2I|5|6|7|5O|8|@]|9|@]|A|$]]|$1|2J|3|2K|5|1S|7|5P|8|@]|9|@]|A|$1T|1U]]|$1|2L|3|2M|5|6|7|5Q|8|@]|9|@]|A|$]]|$1|2N|3|2O|5|6|7|5R|8|@$H|5S|I|5T|J|2P]]|9|@]|A|$]]|$1|2Q|3|2R|5|6|7|5U|8|@]|9|@]|A|$]]|$1|2S|3|-4|5|6|7|5V|8|@]|9|@]|A|$]]|$1|2T|3|2U|5|G|7|5W|8|@]|9|@$H|5X|I|5Y|1|5Z]]|A|$]]|$1|2V|3|2W|5|G|7|60|8|@]|9|@$H|61|I|62|1|63]]|A|$]]|$1|2X|3|-4|5|6|7|64|8|@]|9|@]|A|$]]|$1|2Y|3|-4|5|6|7|65|8|@]|9|@]|A|$]]]|2Z|$30|$5|31|32|33|A|$34|2U]]|35|$5|31|32|33|A|$34|2W]]]]

<h3>Different Environments</h3>

Typically, software will run in different environments:

<ul>
<li><code>development</code></li>
<li><code>testing</code></li>
<li><code>staging</code></li>
<li><code>production</code></li>
</ul>

<h3>Different Dependencies in Different Environments</h3>

The dependencies which are declared in the <code>require</code> section of <code>composer.json</code> are typically dependencies which are required for running an application or a package in 

<ul>
<li><code>staging</code></li>
<li><code>production</code></li>
</ul>

environments, whereas the dependencies declared in the <code>require-dev</code> section are typically dependencies which are required in

<ul>
<li><code>developing</code></li>
<li><code>testing</code></li>
</ul>

environments.

For example, in addition to the packages used for actually running an application, packages might be needed for developing the software, such as:

<ul>
<li><code>friendsofphp/php-cs-fixer</code> (to detect and fix coding style issues)</li>
<li><code>squizlabs/php_codesniffer</code> (to detect and fix coding style issues)</li>
<li><code>phpunit/phpunit</code> (to drive the development using tests)</li>
<li>etc.</li>
</ul>

<h3>Deployment</h3>

Now, in <code>development</code> and <code>testing</code> environments, you would typically run

<pre><code>$ composer install
</code></pre>

to install both <code>production</code> and <code>development</code> dependencies.

However, in <code>staging</code> and <code>production</code> environments, you only want to install dependencies which are required for running the application, and as part of the deployment process, you would typically run

<pre><code>$ composer install --no-dev
</code></pre>

to install only <code>production</code> dependencies.

<h3>Semantics</h3>

In other words, the sections

<ul>
<li><code>require</code></li>
<li><code>require-dev</code></li>
</ul>

indicate to <code>composer</code> which packages should be installed when you run

<pre><code>$ composer install
</code></pre>

or

<pre><code>$ composer install --no-dev
</code></pre>

That is all.

Note Development dependencies of packages your application or package depend on will never be installed

For reference, see:

<ul>
<li><a href="https://getcomposer.org/doc/04-schema.md#require" rel="noreferrer">https://getcomposer.org/doc/04-schema.md#require</a></li>
<li><a href="https://getcomposer.org/doc/04-schema.md#require-dev" rel="noreferrer">https://getcomposer.org/doc/04-schema.md#require-dev</a></li>
</ul>

blocks|key|2779044|text|required部分此部分包含更适合在生产环境中安装/需要的包/依赖项。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2779045|require+dev部分：这个部分包含包/依赖项，开发人员可以使用这些包/依赖项来测试她的代码(或者在她的本地计算机上进行实验，但她不希望在生产环境中安装这些包)。|2779046|entityMap^0|0|A|0|0|E|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

require section
This section contains the packages/dependencies which are better candidates to be installed/required in the production environment.

require-dev section: This section contains the packages/dependencies which can be used by the developer to test her code (or to experiment on her local machine and she doesn't want these packages to be installed on the production environment).

blocks|key|2991686|text|一般规则是，您只在开发(dev)环境中需要来自require+dev部分的包，例如本地环境。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2991687|require+dev部分中的包是帮助您调试应用程序、运行测试等的包。|2991688|在staging和production环境中，您可能只需要中的包需要部分。|2991689|但无论如何，您可以在任何环境上运行composer+install+--no-dev和composer++--no-dev命令将仅从required部分而不是从require-dev，安装软件包，但您可能希望仅在staging和production环境中运行此命令，而不是在本地环境中运行此命令。|2991690|理论上，您可以将所有包放在require部分，并且不会发生任何事情，但您不希望在生产环境中开发包，原因如下：|2991691|公开一些调试info|2991692|etc|unordered-list-item|2991693|
的|2991694|speed|ordered-list-item|2991695|potential|2991696|2991697|require+dev的一些很好的候选者是：|2991698|"filp/whoops":+"%5E2.0",
"fzaninotto/faker":+"%5E1.4",
"mockery/mockery":+"%5E1.0",
"nunomaduro/collision":+"%5E2.0",
"phpunit/phpunit":+"%5E7.0"|code-block|syntax|javascript|2991699|你可以看到上面的包在做什么，你会明白为什么你在生产中不需要它们。|2991700|点击此处查看更多信息：https://getcomposer.org/doc/04-schema.md|2991701|entityMap|0|LINK|mutability|MUTABLE|url|https://getcomposer.org/doc/04-schema.md^0|N|B|0|0|B|0|1|7|9|A|T|5|0|H|P|17|9|1U|8|28|B|2Y|7|36|Y|0|0|1I|0|0|A|0|0|3|0|1|1|0|0|5|0|0|9|0|0|0|M|0|0|0|W|0|0|1F|B|14|0|0^^$0|@$1|2|3|4|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1M|8|@$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1P|8|@$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1W|8|@$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]|$9|21|A|22|B|C]|$9|23|A|24|B|C]|$9|25|A|26|B|C]|$9|27|A|28|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|29|8|@$9|2A|A|2B|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|2C|8|@$9|2D|A|2E|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|R|7|2F|8|@$9|2G|A|2H|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|2I|8|@$9|2J|A|2K|B|C]]|D|@]|E|$]]|$1|U|3|V|5|W|7|2L|8|@$9|2M|A|2N|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|W|7|2O|8|@$9|2P|A|2Q|B|C]]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|2R|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|2S|8|@$9|2T|A|2U|B|C]]|D|@]|E|$]]|$1|12|3|13|5|14|7|2V|8|@]|D|@]|E|$15|16]]|$1|17|3|18|5|6|7|2W|8|@$9|2X|A|2Y|B|C]]|D|@]|E|$]]|$1|19|3|1A|5|6|7|2Z|8|@$9|30|A|31|B|C]]|D|@$9|32|A|33|1|34]]|E|$]]|$1|1B|3|-4|5|6|7|35|8|@]|D|@]|E|$]]]|1C|$1D|$5|1E|1F|1G|E|$1H|1I]]]]

General rule is that you want packages from require-dev section only in development (dev) environments, for example local environment.

Packages in require-dev section are packages which help you debug app, run tests etc.

At staging and production environment you probably want only packages from require section.

But anyway you can run composer install --no-dev and composer update --no-dev on any environment, command will install only packages from required section not from require-dev, but probably you want to run this only at staging and production environments not on local.

Theoretically you can put all packages in require section and nothing will happened, but you don't want developing packages at production environment because of the following reasons : 

<ol>
<li>speed</li>
<li>potential of expose some debuging info</li>
<li>etc</li>
</ol>

Some good candidates for require-dev are : 

<pre><code>"filp/whoops": "^2.0",
"fzaninotto/faker": "^1.4",
"mockery/mockery": "^1.0",
"nunomaduro/collision": "^2.0",
"phpunit/phpunit": "^7.0"
</code></pre>

you can see what above packages are doing and you will see why you don't need them on production.

See more here : <a href="https://getcomposer.org/doc/04-schema.md" rel="nofollow noreferrer">https://getcomposer.org/doc/04-schema.md</a>

blocks|key|172778|text|注意require+dev(仅限根用户)！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|172779|这意味着只有当您的包是整个项目的根时，require-dev部分才有效。例如，如果你从你的包文件夹中运行composer+update。|CODE|172780|如果你为一些主项目开发了一个插件，它有自己的composer.json，那么你的require+dev部分将被完全忽略！如果您需要开发依赖项，则必须将require+dev移到主项目中的composer.json。|172781|entityMap^0|2|I|0|J|B|1G|F|0|14|B|23|B|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$]]

Note the require-dev (root-only) !
which means that the require-dev section is only valid when your package is the root of the entire project. I.e. if you run <code>composer update</code> from your package folder.
If you develop a plugin for some main project, that has it's own composer.json, then your require-dev section will be completely ignored! If you need your developement dependencies, you have to move your require-dev to composer.json in main project.

I'm beginning using composer, I know so little about it and have a little experience with web application development.

I just walk through <a href="http://net.tutsplus.com/tutorials/javascript-ajax/combining-laravel-4-and-backbone/" rel="noreferrer">Nettuts+ Tutorial</a>, so I have basic question about composer.

<pre><code>{
 "require": {
 "laravel/framework": "4.0.*",
 "way/generators": "dev-master",
 "twitter/bootstrap": "dev-master",
 "conarwelsh/mustache-l4": "dev-master"
 },
 "require-dev": {
 "phpunit/phpunit": "3.7.*",
 "mockery/mockery": "0.7.*"
 },
 "autoload": {
 "classmap": [
 "app/commands",
 "app/controllers",
 "app/models",
 "app/database/migrations",
 "app/database/seeds",
 "app/tests/TestCase.php"
 ]
 },
 "scripts": {
 "post-update-cmd": "php artisan optimize"
 },
 "minimum-stability": "dev"
}
</code></pre>

<ol>
<li>Whatever appears in <code>"require-dev"</code> part, will only be downloaded and installed with <code>composer install --dev</code>?</li>
<li>I read some of composer's documentation but still don't understand what is the reason we have <code>"require-dev"</code> part? Is it because of we want to get specific version of the package rather always getting the latest stable version?</li>
</ol>

What is the difference between require and require-dev sections in composer.json?

我开始使用composer，我对它知之甚少，对web应用程序开发也有一些经验。我只是浏览了一下，所以我有一个关于composer的基本问题。{  "require": {    "laravel/framework": "4.0.*",    "way/generators": "dev-master",    "tw...

问composer.json中的require和require dev部分有什么区别？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问composer.json中的require和require dev部分有什么区别？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问composer.json中的require和require dev部分有什么区别？
EN