blocks|key|114024|text|这意味着没有将package.json文件签入到您的git项目的根目录中，因此Heroku检测到它不是Node.js应用程序。您可以在本地查看：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|114025|git+show+master:package.json|code-block|syntax|javascript|114026|要修复它，您需要确保在项目的根目录(其中还有一个.git目录)中有一个package.json，并将其添加到git：|114027|git+add+package.json
git+commit+-m+'track+package.json'|114028|措辞(‘未能检测到set+buildpack')可以改进。它可能会说“未能检测到Node.js应用程序”。当运行构建包的“检测”脚本(https://github.com/heroku/heroku-buildpack-nodejs/blob/master/bin/detect)时，它将查找package.json文件以验证是否有节点应用程序可供构建。|114029|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/heroku/heroku-buildpack-nodejs/blob/master/bin/detect^0|7|C|0|0|0|0|1V|20|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|Q|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

This means that a <code>package.json</code> file isn't checked into the root of your git project, so Heroku is detecting that it isn't a Node.js app. You can see this locally:

<pre><code>git show master:package.json
</code></pre>

To fix it, you'll want to be sure there is a package.json in the root of your project (where there is also a .git directory), and add it to git:

<pre><code>git add package.json
git commit -m 'track package.json'
</code></pre>

The phrasing ('failed to detect set buildpack') could be improved. It should probably say 'failed to detect Node.js app'. When the buildpack's "detect" script is run (<a href="https://github.com/heroku/heroku-buildpack-nodejs/blob/master/bin/detect">https://github.com/heroku/heroku-buildpack-nodejs/blob/master/bin/detect</a>), it looks for a package.json file to verify that there's a node app available to build.

blocks|key|114377|text|我也遇到过类似的问题，下面是解决问题的步骤。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|114378|heroku+buildpacks:set+heroku/nodejs
git+push+heroku+master|code-block|syntax|javascript|114379|基本上详细信息在更多信息链接中-|114380|114381|如果您删除或重命名以前导致自动检测应用程序类型的文件，从而在应用程序上自动设置检测到的构建包，也可能发生这种情况。|114382|114383|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|N|$]]

I had similar issue, here are the steps which solved the problem.

<pre><code>heroku buildpacks:set heroku/nodejs
git push heroku master
</code></pre>

Basically details are in the more info link - 

<hr>

This situation may also occur if you remove or rename a file that previously led to the automatic detection of your application type and thus the automatic setting of the detected buildpack on your application.

<hr>

blocks|key|114387|text|这是因为Heroku认为您正在部署Node应用程序。但您要部署的是节点应用程序的public+，而不是节点代码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|114388|Heroku使用构建包来选择如何处理ap。您想要清除该节点关联：|114389|buildpacks:clear++#+clear+all+buildpacks+set+on+the+app|114390|这意味着“下一版本将正常检测buildpack。”，这应该会为你解决这个问题。|114391|参考：https://devcenter.heroku.com/articles/buildpacks|114392|entityMap|0|LINK|mutability|MUTABLE|url|https://devcenter.heroku.com/articles/buildpacks^0|14|6|14|6|0|0|0|1J|0|0|3|1C|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|11|8|@]|E|@]|F|$]]|$1|I|3|J|5|6|7|12|8|@$9|13|A|14|B|D]]|E|@]|F|$]]|$1|K|3|L|5|6|7|15|8|@]|E|@]|F|$]]|$1|M|3|N|5|6|7|16|8|@]|E|@$9|17|A|18|1|19]]|F|$]]|$1|O|3|-4|5|6|7|1A|8|@]|E|@]|F|$]]]|P|$Q|$5|R|S|T|F|$U|V]]]]

It’s because Heroku thinks you are deploying a Node app. But what you are deploying is the <code>public</code> directory of a Node app, not Node code.

Heroku uses buildpacks to select how the ap is handled. You want to clear that Node association:

<code>buildpacks:clear # clear all buildpacks set on the app</code>

Which means that “Next release will detect buildpack normally.”, that should solve it for you.

ref: <a href="https://devcenter.heroku.com/articles/buildpacks" rel="noreferrer">https://devcenter.heroku.com/articles/buildpacks</a>

blocks|key|2870179|text|对其他答案进行一些细微的澄清:错误“未能检测到set+buildpack+https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/nodejs.tgz”或任何类似的错误，意思是说您试图推送给heroku的GIT提交没有作为node.js应用程序被检测到。(请注意大写的微妙之处)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2870180|我最近犯了一个愚蠢的错误，这让我意识到这一点:运行"ls+heroku“显示我的package.json和.git文件在相同的根目录中，正如-a所要求的那样。除了package.json文件没有包含在我最新的git提交中。运行"git+status“提示我package.json是一个未被跟踪的文件。所以我添加了它，ta-da，推到heroku起作用了。|2870181|如果您得到一个与构建包相关的错误，请检查您的GIT提交在根目录中是否有一个package.json文件。如果这是真的，请尝试使用"heroku+buildpacks:set+heroku/nodejs“(或您所需的语言)手动指定构建包。这应该可以解决大多数与构建包检测相关的错误。|2870182|entityMap|0|LINK|mutability|MUTABLE|url|https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/nodejs.tgz^0|11|1Y|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

Some tiny clarifications on other answers:
The error "Failed to detect set buildpack https://codon-buildpacks.s3.amazonaws&period;com/buildpacks/heroku/nodejs.tgz" or anything similar, means to say the GIT COMMIT you are trying to push to heroku was not DETECTED as a node.js app. (Note the capitals for subtleties).

I recently made a stupid mistake that made me aware of this: Running "ls -a" showed that my package.json and .git files were in the same root directory, as required by heroku. EXCEPT that the package.json file WAS NOT included in my latest git commit. Running "git status" alerted me that package.json was an untracked file. So I added it, and ta-da, pushing to heroku worked. 

If you get an error related to buildpack, check that your GIT COMMIT has a package.json file in the root directory. If this is true, try manually specifying the buildpack with "heroku buildpacks:set heroku/nodejs" (or your desired language). This should resolve most errors related to buildpack detection.

blocks|key|112100|text|如果您正在处理分支，则需要设置master来跟踪您的分支|type|unstyled|depth|inlineStyleRanges|entityRanges|data|112101|git+branch+-f+--track+master+origin/branch_name|offset|length|style|CODE|112102|在master中检查package.json|112103|git+show+master:package.json|112104|如果可用，请再次尝试推送。|112105|git+push+heroku+master|112106|`|112107|entityMap^0|0|0|1B|0|0|0|S|0|0|0|M|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|S|$]]

If you are working on a branch, you need to set master to track your branch

<code>git branch -f --track master origin/branch_name</code>

Check for package.json in master

<code>git show master:package.json</code>

If it's available, trying pushing again.

<code>git push heroku master</code>

`

blocks|key|114114|text|大多数应用程序至少有一个签名，所以如果你看到这个错误，通常意味着一个重要的文件没有签入到你的git库中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|114115|管道|114116|Java:+pom.xml|unordered-list-item|114117|
|114118|Ruby:+Gemfile|114119|114120|Node.js:+package.json|114121|114122|Python:+requirements.txt+/+setup.py+/|114123|PHP:+composer.json+/+index.php|114124|114125|114126|您应该：|114127|git+add+{file}
git+commit+-am+'added+{file}+
git+push+heroku+master|code-block|syntax|javascript|114128|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|17|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|19|8|@]|9|@]|A|$]]|$1|N|3|H|5|6|7|1A|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|1B|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1C|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|X|5|Y|7|1G|8|@]|9|@]|A|$Z|10]]|$1|11|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|12|$]]

Most apps have at least one of these signatures present, so if you see this error, it usually means an important file isn't checked into your git repository:

<ul>
<li>Java: pom.xml</li>
<li>Ruby: Gemfile</li>
<li>Node.js: package.json</li>
<li>Python: requirements.txt / setup.py / Pipfile</li>
<li>PHP: composer.json / index.php</li>
</ul>

You should:

<pre><code>git add {file}
git commit -am 'added {file} 
git push heroku master
</code></pre>

blocks|key|2659259|text|我遇到了同样的问题，并尝试了所有方法，最终意识到没有文件会提交，因为它们已经提交并推送到github存储库。因此，您需要执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2659260|2659261|删除旧的git。文件夹：|unordered-list-item|2659262|2659263|2659264|+rm+-rf+.git|blockquote|2659265|2659266|2659267|2659268|创建新的git:|2659269|2659270|2659271|+git初始化|2659272|2659273|2659274|2659275|添加所有项目文件：|2659276|2659277|2659278|+git+add+.|2659279|2659280|2659281|2659282|Commit:|2659283|2659284|2659285|+git提交名称“commit+-m”|2659286|2659287|2659288|2659289|创建新的heroku+application:|2659290|2659291|2659292|+heroku创建|2659293|2659294|2659295|2659296|推送代码给master:|2659297|2659298|2659299|+git推送heroku+master|2659300|2659301|2659302|这对我很有效。|2659303|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|20|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|21|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|24|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|28|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|29|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|R|3|S|5|J|7|2B|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|2D|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|W|3|X|5|E|7|2F|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]|$1|10|3|11|5|J|7|2I|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2J|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|2L|8|@]|9|@]|A|$]]|$1|15|3|16|5|E|7|2M|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]|$1|19|3|1A|5|J|7|2P|8|@]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|E|7|2T|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|2U|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|J|7|2W|8|@]|9|@]|A|$]]|$1|1K|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]|$1|1L|3|-4|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|E|7|30|8|@]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|31|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|32|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|J|7|33|8|@]|9|@]|A|$]]|$1|1T|3|-4|5|6|7|34|8|@]|9|@]|A|$]]|$1|1U|3|-4|5|6|7|35|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|6|7|36|8|@]|9|@]|A|$]]|$1|1X|3|-4|5|6|7|37|8|@]|9|@]|A|$]]]|1Y|$]]

I run into the same issue and tried everything, eventually realized no file would commit because they were already committed and pushed to the github repository.
So you need to do the following:

<ul>
<li>Remove old git. folder:</li>
</ul>

<blockquote>
 rm -rf .git
</blockquote>

<ul>
<li>Create new git:</li>
</ul>

<blockquote>
 git init
</blockquote>

<ul>
<li>Add all project files:</li>
</ul>

<blockquote>
 git add .
</blockquote>

<ul>
<li>Commit:</li>
</ul>

<blockquote>
 git commit -m “commit name”
</blockquote>

<ul>
<li>Creat new heroku application:</li>
</ul>

<blockquote>
 heroku create
</blockquote>

<ul>
<li>Push code to master:</li>
</ul>

<blockquote>
 git push heroku master
</blockquote>

This worked for me.

blocks|key|2870285|text|我添加了Pakage.json文件，然后|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2870286|删除旧的git。文件夹:+rm+-rf+.git|2870287|创建新的git:+git+init|2870288|添加所有项目文件:+git+Add。|2870289|Commit:+git+commit+-m“提交名称”|2870290|创建新heroku应用程序:+heroku+create|2870291|向master推送代码:+git+Push+heroku+master|2870292|已在heroku上成功部署应用程序。|2870293|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I add Pakage.json file, and then
Remove old git. folder:
rm -rf .git
Create new git:
git init
Add all project files:
git add .
Commit:
git commit -m “commit name”
Creat new heroku application:
heroku create
Push code to master:
git push heroku master
App successfully deployed on heroku.

I git cloned a Node.js application (the version specified in the <code>package.json</code> being <code>4.1.2</code> and that of my local machine being <code>6.2.2</code>) and tried to git push on Heroku. But it failed to build and gave this error:

<blockquote>
 Failed to detect set buildpack https://codon-buildpacks.s3.amazonaws&period;com/buildpacks/heroku/nodejs.tgz
</blockquote>

Now I set the buildpack to heroku/nodejs and I get this message:

<pre><code>Buildpack set. Next release on lit-badlands-92088 will use heroku/nodejs.
Run git push heroku master to create a new release using this buildpack.
</code></pre>

Now when I run <code>git push heroku master</code>, I am again told:

<pre><code>remote: -----&gt; Failed to detect set buildpack
 https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/nodejs.tgz 

remote: More info: 
https://devcenter.heroku.com/articles/buildpacks#detection-failure 

remote: 
remote: ! Push failed 
remote: Verifying deploy... 
remote: 
remote: ! Push rejected to lit-badlands-92088.
</code></pre>

What could be the possible reasons for the Node.js buildpack not being detected even if I set it?

Why does Heroku fail to detect Node.js buildpack?

Java

我git克隆了一个Node.js应用程序(在package.json中指定的版本是4.1.2，我的本地机器的版本是6.2.2)，并尝试在Heroku上使用git推送。但是它构建失败，并给出了这个错误：检测set buildpack 失败现在我将buildpack设置为heroku/nodejs，并收到以下消息：Buil...

问为什么Heroku无法检测到Node.js构建包？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么Heroku无法检测到Node.js构建包？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为什么Heroku无法检测到Node.js构建包？
EN