【问题标题】:Need help deploying full stack website to heroku: Error: There is likely additional logging output above需要帮助将全栈网站部署到heroku:错误:上面可能有额外的日志输出
【发布时间】:2022-01-04 16:01:22
【问题描述】:

我是全栈开发的新手,一直在尝试将我的网站上传到 heroku,我收到此错误消息,我猜它与根文件夹中的 package-lock.json 文件有关。

我在一个父文件夹下同时拥有前端和后端文件夹。 如果您可以查看,这里是小项目的链接:https://github.com/manuelmort/tft-project

我通常会将一些小网站上传到 gh-pages,但由于它们不支持服务器端代码,我必须使用 heroku。它构建成功,但由于 heroku CLI 上的以下错误消息,该站点永远不会启动

2022-01-04T16:23:14.000000+00:00 app[api]: Build started by user manuelmort@gmail.com
2022-01-04T16:24:54.111750+00:00 app[api]: Deploy 8cc070c4 by user manuelmort@gmail.com
2022-01-04T16:24:54.111750+00:00 app[api]: Release v13 created by user manuelmort@gmail.com
2022-01-04T16:24:57.562224+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-04T16:25:02.000000+00:00 app[api]: Build succeeded
2022-01-04T16:25:04.610196+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-04T16:25:07.018112+00:00 app[web.1]: 
2022-01-04T16:25:07.018129+00:00 app[web.1]: > tft-project@1.0.0 start /app
2022-01-04T16:25:07.018130+00:00 app[web.1]: > concurrently "npm run backend" "npm run client"
2022-01-04T16:25:07.018130+00:00 app[web.1]: 
2022-01-04T16:25:07.022660+00:00 app[web.1]: sh: 1: concurrently: not found
2022-01-04T16:25:07.028749+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-04T16:25:07.028977+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-04T16:25:07.029095+00:00 app[web.1]: npm ERR! file sh
2022-01-04T16:25:07.029286+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-04T16:25:07.034404+00:00 app[web.1]: npm ERR! tft-project@1.0.0 start: `concurrently "npm run backend""npm run client"`
2022-01-04T16:25:07.034446+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-04T16:25:07.034492+00:00 app[web.1]: npm ERR!
2022-01-04T16:25:07.034537+00:00 app[web.1]: npm ERR! Failed at the tft-project@1.0.0 start script.
2022-01-04T16:25:07.034580+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likelyadditional logging output above.
2022-01-04T16:25:07.040214+00:00 app[web.1]: 
2022-01-04T16:25:07.040320+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-04T16:25:07.040356+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2022-01-04T16_25_07_034Z-debug.log
2022-01-04T16:25:07.238236+00:00 heroku[web.1]: Process exited with status 1
2022-01-04T16:25:07.301484+00:00 heroku[web.1]: State changed from starting to crashed
2022-01-04T16:25:07.307500+00:00 heroku[web.1]: State changed from crashed to starting
2022-01-04T16:25:15.521992+00:00 heroku[web.1]: Starting process with command `npm start`
2022-01-04T16:25:17.284061+00:00 app[web.1]: 
2022-01-04T16:25:17.284072+00:00 app[web.1]: > tft-project@1.0.0 start /app
2022-01-04T16:25:17.284073+00:00 app[web.1]: > concurrently "npm run backend" "npm run client"
2022-01-04T16:25:17.284073+00:00 app[web.1]:
2022-01-04T16:25:17.298996+00:00 app[web.1]: sh: 1: concurrently: not found
2022-01-04T16:25:17.316611+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2022-01-04T16:25:17.317012+00:00 app[web.1]: npm ERR! syscall spawn
2022-01-04T16:25:17.317189+00:00 app[web.1]: npm ERR! file sh
2022-01-04T16:25:17.317369+00:00 app[web.1]: npm ERR! errno ENOENT
2022-01-04T16:25:17.337279+00:00 app[web.1]: npm ERR! tft-project@1.0.0 start: `concurrently "npm run backend""npm run client"`
2022-01-04T16:25:17.337583+00:00 app[web.1]: npm ERR! spawn ENOENT
2022-01-04T16:25:17.337807+00:00 app[web.1]: npm ERR!
2022-01-04T16:25:17.337920+00:00 app[web.1]: npm ERR! Failed at the tft-project@1.0.0 start script.
2022-01-04T16:25:17.338041+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likelyadditional logging output above.
2022-01-04T16:25:17.347983+00:00 app[web.1]:
2022-01-04T16:25:17.350592+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2022-01-04T16:25:17.350682+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2022-01-04T16_25_17_338Z-debug.log
2022-01-04T16:25:17.534240+00:00 heroku[web.1]: Process exited with status 1
2022-01-04T16:25:17.755577+00:00 heroku[web.1]: State changed from starting to crashed

任何帮助将不胜感激!

【问题讨论】:

  • 引用:This is probably not a problem with npm. There is likely additional logging output above.
  • 这里没有有用的信息。
  • 刚刚更新了日志。还有什么我应该展示的东西来提供关于我的问题的更多信息,不知道我是否向你们展示了正确的日志
  • concurrently: not found——看起来concurrently 不可用。请出示您的package.json
  • 我提供了项目的github链接

标签: node.js reactjs npm heroku package-lock.json


【解决方案1】:

原来我需要在 package.json 文件中同时具有依赖项而不是 devDependecies 分支, 我不再收到错误了

【讨论】:

    猜你喜欢
    • 2019-12-27
    • 1970-01-01
    • 2019-08-30
    • 1970-01-01
    • 2015-01-13
    • 1970-01-01
    • 2020-11-16
    • 1970-01-01
    • 2021-02-13
    相关资源
    最近更新 更多