-
Notifications
You must be signed in to change notification settings - Fork 750
Open
Description
When deploying this to Heroku, an error occurs in which the following log is produced:
2018-12-01T01:37:29.263070+00:00 heroku[web.1]: Starting process with command `npm start`
2018-12-01T01:37:27.000000+00:00 app[api]: Build succeeded
2018-12-01T01:37:32.506185+00:00 heroku[web.1]: Process exited with status 1
2018-12-01T01:37:32.359519+00:00 app[web.1]:
2018-12-01T01:37:32.359538+00:00 app[web.1]: > react-redux-registration-login-example@1.0.0 start /app
2018-12-01T01:37:32.359540+00:00 app[web.1]: > webpack-dev-server --open
2018-12-01T01:37:32.359541+00:00 app[web.1]:
2018-12-01T01:37:32.394066+00:00 app[web.1]: sh: 1: webpack-dev-server: not found
2018-12-01T01:37:32.401497+00:00 app[web.1]: npm ERR! file sh
2018-12-01T01:37:32.401869+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2018-12-01T01:37:32.402180+00:00 app[web.1]: npm ERR! errno ENOENT
2018-12-01T01:37:32.402494+00:00 app[web.1]: npm ERR! syscall spawn
2018-12-01T01:37:32.407459+00:00 app[web.1]: npm ERR! react-redux-registration-login-example@1.0.0 start: `webpack-dev-server --open`
2018-12-01T01:37:32.407725+00:00 app[web.1]: npm ERR! spawn ENOENT
2018-12-01T01:37:32.408144+00:00 app[web.1]: npm ERR!
2018-12-01T01:37:32.408387+00:00 app[web.1]: npm ERR! Failed at the react-redux-registration-login-example@1.0.0 start script.
2018-12-01T01:37:32.408605+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
It looks like there is a problem with webpack-dev-server. Is there any way to fix this, and if so, how?
Metadata
Metadata
Assignees
Labels
No labels