[Debugging] Can't push to Heroku master.

This page summarizes the projects mentioned and recommended in the original post on /r/learnprogramming

InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • YTS-Movie-App

  • To explain, I have built a simple web app that brings the movie data from my Node express server using proxy. For the original working repository(https://github.com/PricelessCode/YTS-Movie-App), I have separated the client-side code(React)(folder name: movie-app) and the server-side code(Node)(folder name: server). After finished developing, since I wanted to deploy the app to the Heroku server, I decided to make a build version out of the client-side code and put it inside the server directory(I used npm run build).

  • heroku-movie-app

  • To deploy the app using Heroku, I have created another repo(https://github.com/PricelessCode/heroku-movie-app) that is directly connected to the Heroku server. However, whenever I try to push to the heroku master, errors show up like below everytime keeping me from pushing.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • node-sass

    :rainbow: Node.js bindings to libsass

  • -----> Building on the Heroku-20 stack -----> Using buildpack: heroku/nodejs -----> Node.js app detected -----> Creating runtime environment NPM_CONFIG_LOGLEVEL=error NODE_VERBOSE=false NODE_ENV=production NODE_MODULES_CACHE=true -----> Installing binaries engines.node (package.json): unspecified engines.npm (package.json): unspecified (use default) Resolving node version 14.x... Downloading and installing node 14.17.0... Using default npm version: 6.14.13 -----> Installing dependencies Installing node modules > [email protected] postinstall /tmp/build_00fa5d5a/node_modules/babel-runtime/node_modules/core-js > node -e "try{require('./postinstall')}catch(e){}" > [email protected] install /tmp/build_00fa5d5a/node_modules/chokidar/node_modules/fsevents > node install.js Skipping 'fsevents' build as platform linux is not supported > [email protected] postinstall /tmp/build_00fa5d5a/node_modules/core-js > node -e "try{require('./postinstall')}catch(e){}" > [email protected] install /tmp/build_00fa5d5a/node_modules/jest-haste-map/node_modules/fsevents > node install.js Skipping 'fsevents' build as platform linux is not supported > node-sass@4.14.1 install /tmp/build_00fa5d5a/node_modules/node-sass > node scripts/install.js Downloading binary from https://github.com/sass/node-sass/releases/download/v4.14.1/linux-x64-83_binding.node Download complete Binary saved to /tmp/build_00fa5d5a/node_modules/node-sass/vendor/linux-x64-83/binding.node Caching binary to /tmp/npmcache.CMUgS/_cacache/node-sass/4.14.1/linux-x64-83_binding.node > node-sass@4.14.1 postinstall /tmp/build_00fa5d5a/node_modules/node-sass > node scripts/build.js Binary found at /tmp/build_00fa5d5a/node_modules/node-sass/vendor/linux-x64-83/binding.node Testing binary Binary is fine added 1673 packages in 22.719s -----> Build Running build > [email protected] build /tmp/build_00fa5d5a > react-scripts build Could not find a required file. Name: index.html Searched in: /tmp/build_00fa5d5a/public npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] build: `react-scripts build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /tmp/npmcache.CMUgS/_logs/2021-06-05T16_00_38_222Z-debug.log -----> Build failed We're sorry this build is failing! You can troubleshoot common issues here: https://devcenter.heroku.com/articles/troubleshooting-node-deploys Some possible problems: - Node version not specified in package.json https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version Love, Heroku ! Push rejected, failed to compile Node.js app. ! Push failed

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • 'npm install' attempts to download an non-existent 'win32-x64-83_binding.node' file.

    2 projects | /r/AskProgramming | 1 Jun 2022
  • "Precompiling assets failed" error when pushing to heroku

    1 project | /r/rails | 18 Feb 2022
  • Trying to run older react app that uses node-sass

    1 project | /r/reactjs | 15 Feb 2022
  • HELP! Macbook m1 problem on docker (node-sass not found)

    1 project | /r/docker | 24 Apr 2021
  • node-sass: Build fails on OpenBSD - How to fix

    2 projects | dev.to | 23 Feb 2022