blocks|key|120573|text|确保您没有将环境变量NODE_ENV设置为'production‘。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|120574|如果这样做，则不会在没有--dev标志的情况下安装开发依赖项|120575|entityMap^0|A|8|0|C|5|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|$]]

make sure you don't have env variable <code>NODE_ENV</code> set to 'production'.

If you do, dev dependencies will not be installed without the <code>--dev</code> flag

blocks|key|119795|text|检查NPM文档中的install|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|119796|带有--production标志的|style|CODE|119797|+(或当NODE_ENV环境变量设置为production时)，npm将不会安装devDependencies中列出的模块。“|blockquote|119798|119799|无论NODE_ENV是什么，--only={prod[uction]%7Cdev[elopment]}参数都将导致仅安装devDependencies或仅安装非devDependencies。“|119800|119801|你试过了吗？|119802|npm+install+--only=dev|code-block|syntax|javascript|119803|如果您担心您的package.json可能不正确，最好的做法是这样做。创建一个新文件夹，然后运行：|BOLD|119804|npm+init+--yes|119805|然后：|119806|npm+install+--save-dev+brunch@%5E2.0.4
npm+install+--save-dev+cssnano-brunch@%5E1.1.5
npm+install+--save-dev+javascript-brunch@%5E1.8.0
npm+install+--save-dev+sass-brunch@%5E1.9.2
npm+install+--save-dev+uglify-js-brunch@%5E1.7.8
npm+install+jquery@%5E2.1.4+--save|119807|你应该可以走了！否则，将继续张贴其他选项。|119808|检查您的npm配置：|119809|npm+config+list|119810|npm从命令行、环境变量和npmrc文件获取其配置设置。因此，请检查环境变量和npmrc文件。|119811|仍在失败？|119812|好的，创建一个新文件夹，最好是文件系统上的其他位置。即。不在同一文件夹层次结构中。例如，C:\myNewFolder+-离基本C:驱动器越近越好。|119813|然后运行：|119814|npm+init+--yes|119815|现在运行：|119816|npm+install+underscore+--save|119817|最后：|119818|npm+install+mocha+--save-dev|119819|一切都像预期的那样工作吗？|119820|我想要做的是了解您的问题是全局的，还是前一个文件夹和依赖项的局部问题。|119821|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.npmjs.com/cli/install|1|https://docs.npmjs.com/files/npmrc^0|9|7|0|0|2|C|0|0|0|E|Z|0|0|0|0|7|C|0|0|0|0|0|0|0|13|5|1|0|0|5|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|26|8|@]|9|@$A|27|B|28|1|29]]|C|$]]|$1|D|3|E|5|6|7|2A|8|@$A|2B|B|2C|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|2D|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|2E|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|2F|8|@$A|2G|B|2H|F|G]]|9|@]|C|$]]|$1|N|3|-4|5|6|7|2I|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|2J|8|@]|9|@]|C|$]]|$1|Q|3|R|5|S|7|2K|8|@]|9|@]|C|$T|U]]|$1|V|3|W|5|6|7|2L|8|@$A|2M|B|2N|F|X]]|9|@]|C|$]]|$1|Y|3|Z|5|S|7|2O|8|@]|9|@]|C|$T|U]]|$1|10|3|11|5|6|7|2P|8|@]|9|@]|C|$]]|$1|12|3|13|5|S|7|2Q|8|@]|9|@]|C|$T|U]]|$1|14|3|15|5|6|7|2R|8|@]|9|@]|C|$]]|$1|16|3|17|5|6|7|2S|8|@]|9|@]|C|$]]|$1|18|3|19|5|S|7|2T|8|@]|9|@]|C|$T|U]]|$1|1A|3|1B|5|6|7|2U|8|@]|9|@$A|2V|B|2W|1|2X]]|C|$]]|$1|1C|3|1D|5|6|7|2Y|8|@$A|2Z|B|30|F|X]]|9|@]|C|$]]|$1|1E|3|1F|5|6|7|31|8|@]|9|@]|C|$]]|$1|1G|3|1H|5|6|7|32|8|@]|9|@]|C|$]]|$1|1I|3|1J|5|S|7|33|8|@]|9|@]|C|$T|U]]|$1|1K|3|1L|5|6|7|34|8|@]|9|@]|C|$]]|$1|1M|3|1N|5|S|7|35|8|@]|9|@]|C|$T|U]]|$1|1O|3|1P|5|6|7|36|8|@]|9|@]|C|$]]|$1|1Q|3|1R|5|S|7|37|8|@]|9|@]|C|$T|U]]|$1|1S|3|1T|5|6|7|38|8|@]|9|@]|C|$]]|$1|1U|3|1V|5|6|7|39|8|@]|9|@]|C|$]]|$1|1W|3|-4|5|6|7|3A|8|@]|9|@]|C|$]]]|1X|$1Y|$5|1Z|20|21|C|$22|23]]|24|$5|1Z|20|21|C|$22|25]]]]

Check the NPM docs for <a href="https://docs.npmjs.com/cli/install" rel="noreferrer">install</a>
<blockquote>
With the <code>--production</code> flag (or when the NODE_ENV environment variable is set to production), npm will not install modules listed in devDependencies.&quot;
The <code>--only={prod[uction]|dev[elopment]}</code> argument will cause either only devDependencies or only non-devDependencies to be installed regardless of the NODE_ENV.&quot;
</blockquote>
Have you tried
<pre><code>npm install --only=dev
</code></pre>
If you are worried that your package.json might be incorrect, best thing to do is this. Create a new folder, and run:
<pre><code>npm init --yes
</code></pre>
Then:
<pre><code>npm install --save-dev brunch@^2.0.4
npm install --save-dev cssnano-brunch@^1.1.5
npm install --save-dev javascript-brunch@^1.8.0
npm install --save-dev sass-brunch@^1.9.2
npm install --save-dev uglify-js-brunch@^1.7.8
npm install jquery@^2.1.4 --save
</code></pre>
And you should be good to go! Otherwise, will keep posting other options.
Check your npm configuration:
<pre><code>npm config list
</code></pre>
npm gets its config settings from the command line, environment variables, and npmrc files. So check environment variables, and the <a href="https://docs.npmjs.com/files/npmrc" rel="noreferrer">npmrc</a> file.
Still failing?
Ok, create a new folder, ideally somewhere else on your filesystem. ie. not in same folder hierarchy. For instance, C:\myNewFolder - the closer to the base C: drive the better.
Then run:
<pre><code>npm init --yes
</code></pre>
Now run:
<pre><code>npm install underscore --save
</code></pre>
and finally:
<pre><code>npm install mocha --save-dev
</code></pre>
Does everything work as expected?
What I am trying to do is understand whether your problem is global, or something local to the previous folder and dependencies.

blocks|key|2886421|text|检查npm+config+production值是否设置为true。如果此值为true，它将跳过dev依赖项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2886422|运行npm+config+get+production|offset|length|style|CODE|2886423|要设置它：npm+config+set+-g+production+false|2886424|entityMap^0|0|2|P|0|5|Y|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

Check if npm config production value is set to true. If this value is true, it will skip over the dev dependencies.

Run <code>npm config get production</code>

To set it: <code>npm config set -g production false</code>

blocks|key|2886443|text|我有一个来自旧版本package.json的package-lock.json文件，我删除了它，然后一切都安装正确了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2886444|entityMap^0|M|H|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

I had a <code>package-lock.json</code> file from an old version of my package.json, I deleted that and then everything installed correctly.

blocks|key|119838|text|您可以使用安装依赖的快捷方式仅用于开发，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|119839|npm+i+-D+<dependencies-names>|code-block|syntax|javascript|119840|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can use the short way for installation dependencies only for development as follows:

<pre><code>npm i -D &lt;dependencies-names&gt;
</code></pre>

blocks|key|2886462|text|确保您的package.json有效...|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2886463|我有以下错误...|2886464|npm+WARN+Invalid+name:+"blah+blah+blah"|2886465|同样，这也导致devDependencies无法安装。|2886466|仅供参考，将package.json+"name“更改为blah-blah-blah修复了该问题。|2886467|entityMap^0|4|C|0|0|0|13|0|7|F|0|6|C|S|E|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|O|$]]

Make sure your <code>package.json</code> is valid...

I had the following error...

<code>npm WARN Invalid name: "blah blah blah"</code>

and that, similarly, caused <code>devDependencies</code> not to be installed.

FYI, changing the <code>package.json</code> "name" to <code>blah-blah-blah</code> fixed it.

blocks|key|2675165|text|我也遇到过类似的问题。npm+install+--only=dev不工作，npm+rebuild也不工作。最终，我不得不删除node_modules和package-lock.json并再次运行npm+install。帮我修好了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2675166|entityMap^0|B|M|11|B|1Q|C|23|H|2P|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|G|$]]

I had a similar problem. <code>npm install --only=dev</code> didn't work, and neither did <code>npm rebuild</code>. Ultimately, I had to delete <code>node_modules</code> and <code>package-lock.json</code> and run <code>npm install</code> again. That fixed it for me.

blocks|key|120598|text|我也有同样的问题，因为我在构建Docker时设置了NODE_ENV=production。然后我再添加一个npm+install+--only=dev。一切都很好。我需要用于构建TypeSciprt模块的devDependencies|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|120599|RUN+npm+install
RUN+npm+install+--only=dev|code-block|syntax|javascript|120600|entityMap^0|P|J|1H|M|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

I have the same issue because I set the <code>NODE_ENV=production</code> while building Docker. Then I add one more <code>npm install --only=dev</code>. Everything works fine. I need the devDependencies for building TypeSciprt modules

<pre><code>RUN npm install
RUN npm install --only=dev
</code></pre>

blocks|key|2675217|text|因此，我解决这个问题的方法是在通常运行npm+install或npm+ci的命令中添加NODE_ENV=build，然后在命令后添加NODE_ENV=production，因此我的整个命令如下：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2675218|RUN+NODE_ENV=build+&&+npm+ci+&&+NODE_ENV=production|code-block|syntax|javascript|2675219|到目前为止，我没有任何不良反应，我用于构建应用程序的开发依赖项都可以正常工作/加载。|2675220|我发现这比添加像npm+install+--only=dev这样的命令是更好的解决方案，因为它花费的时间更少，并且使我能够使用npm+ci命令，该命令速度更快，并且专门设计为在CI工具/构建脚本中运行。(有关详细信息，请参阅npi-ci文档)|2675221|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.npmjs.com/cli/ci.html^0|J|B|V|6|17|E|1U|J|0|0|0|8|M|1R|6|34|6|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|15|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|16|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|O|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

So the way I got around this was in the command where i would normally run <code>npm install</code> or <code>npm ci</code>, i added <code>NODE_ENV=build</code>, and then <code>NODE_ENV=production</code> after the command, so my entire command came out to:
<pre><code>RUN NODE_ENV=build &amp;&amp; npm ci &amp;&amp; NODE_ENV=production
</code></pre>
So far I haven't had any bad reactions, and my development dependencies which are used for building the application all worked / loaded correctly.
I find this to be a better solution than adding an additional command like <code>npm install --only=dev</code> because it takes less time, and enables me to use the <code>npm ci</code> command, which is faster and specifically designed to be run inside CI tools / build scripts. (See <a href="https://docs.npmjs.com/cli/ci.html" rel="nofollow noreferrer">npi-ci</a> documentation for more information on it)

blocks|key|120640|text|运行npm-check-updates+-u后出现类似的错误。已通过删除node_modules文件夹和package-lock.json解决此问题。在那之后，有了新的npm+install，一切都正常了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|120641|我的例外是：|120642|120643|无法加载'package.json»eslint--react-app#overrides‘中声明的分析器'@typescript-eslint/+parser’：找不到模块'@typescript-eslint/parser'|blockquote|120644|120645|entityMap^0|2|K|10|C|1G|H|2C|B|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|Z|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|10|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$]]

Got a similar error after running <code>npm-check-updates -u</code>. Solved it by removing <code>node_modules</code> folder and <code>package-lock.json</code>. After that a new <code>npm install</code> and everything worked.
My exception:
<blockquote>
Failed to load parser '@typescript-eslint/parser' declared in
'package.json » eslint-config-react-app#overrides[0]': Cannot find
module '@typescript-eslint/parser'
</blockquote>

blocks|key|120647|text|在我的例子中，问题是在运行npm+install的同一终端会话中，我将NODE_ENV变量设置为production。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|120648|为了让我的构建正常运行，我不允许修改NODE_ENV的值，所以我强制npm通过添加--production=false标志来安装所有依赖项：npm+install+--production=false+as+mentioned+in+the+docs。|120649|如果不需要将NODE_ENV设置为production，则只需在终端中输入export+NODE_ENV=development以覆盖其值并再次运行npm+install即可。|120650|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.npmjs.com/cli/v8/commands/npm-install^0|D|B|Z|8|0|I|8|15|I|1Y|U|2W|L|0|0|6|8|H|A|11|R|22|B|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|H|3|I|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

In my case, the problem was that I had the <code>NODE_ENV</code> variable set to production in the same terminal session I ran <code>npm install</code>.
For my build to run properly I was not allowed to change the value of <code>NODE_ENV</code> so I forced npm to install all the dependencies by adding the <code>--production=false</code> flag to it: <code>npm install --production=false</code> as <a href="https://docs.npmjs.com/cli/v8/commands/npm-install" rel="nofollow noreferrer">mentioned in the docs</a>.
If you don't need <code>NODE_ENV</code> to be set to <code>production</code> you can simply type <code>export NODE_ENV=development</code> to your terminal to overwrite its value and run <code>npm install</code> again.

On windows for some reason when I run <code>npm install</code> it won't install devDependencies. AFAIK it should. If I run <code>npm install --dev</code> devDependencies are installed. I don't understand why <code>npm install</code> doesn't install devDependencies too, but installs only dependencies. What could be the reason? How can I fix it?

Maybe something is wrong with my package.json? It is listed below if it may be helpful:

<pre><code>{
 "name": "try-brunch",
 "version": "0.1.0",
 "private": "true",
 "devDependencies": {
 "brunch": "^2.0.4",
 "cssnano-brunch": "^1.1.5",
 "javascript-brunch": "^1.8.0",
 "sass-brunch": "^1.9.2",
 "uglify-js-brunch": "^1.7.8"
 },
 "dependencies": {
 "jquery": "^2.1.4"
 }
}
</code></pre>

npm install won't install devDependencies

文件系统

在devDependencies.上，由于某种原因，当我运行npm install时，它不能安装windowsAFAIK它应该。如果我运行npm install --dev，则会安装devDependencies。我不明白为什么npm install不安装devDependencies，而只安装依赖项。可能的原因是什么...

问npm安装不会安装devDependencies
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问npm安装不会安装devDependenciesEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问npm安装不会安装devDependencies
EN