----------> Pruning devDependencies
audited 53 packages in 0.841s
1 package is looking for funding
run `npm fund` for details
found 0 vulnerabilities
----------> Build succeeded!
! This app may not specify any way to start a node process devcenter.heroku.com/articles/node...
----------> Discovering process types
Procfile declares types -> (none)
Default types for buildpack -> web
----------> Compressing...
Done: 22.8M
----------> Launching...
Released v3 twitter0282.herokuapp.com/ deployed to Heroku
So your project might vary - my server project doesn't have a start command that Heroku deals with. It just needs access to the GitHub repo.
This error looks like it can't find a start command. That'll be in your package.json file if it exists. If it's there, you might try running npm run start - the run command is necessary for most npm scripts, though sometimes start will work without it.
Hope that helps! From your other comment, it looks like your build succeeded, so hopefully you're able to move forward!
Hi Jeff - Did you check what your log said, the one mentioned in that error message? What's it telling you?
I tried to correct the error on the port and updated it and this is now what I got on the logs:
-----> Building on the Heroku-20 stack
-----> Node.js app detected
----------> Creating runtime environment
----------> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
----------> Installing dependencies
Installing node modules
added 53 packages in 1.052s
----------> Build
----------> Caching build
- node_modules
----------> Pruning devDependencies
audited 53 packages in 0.841s
----------> Build succeeded!
! This app may not specify any way to start a node process
devcenter.heroku.com/articles/node...
----------> Discovering process types
Procfile declares types -> (none)
Default types for buildpack -> web
----------> Compressing...
Done: 22.8M
----------> Launching...
Released v3
twitter0282.herokuapp.com/ deployed to Heroku
Hi, thanks for the reply. Here's what I got:
dev-to-uploads.s3.amazonaws.com/i/...
So your project might vary - my server project doesn't have a
start
command that Heroku deals with. It just needs access to the GitHub repo.This error looks like it can't find a
start
command. That'll be in your package.json file if it exists. If it's there, you might try runningnpm run start
- therun
command is necessary for most npm scripts, though sometimes start will work without it.Hope that helps! From your other comment, it looks like your build succeeded, so hopefully you're able to move forward!
Cool! I'll try that
Still not working. Hmmm.
Sorry I can't be of more help! Keep searching and troubleshooting, I'm sure you'll get it figured out!
Thank you so much!