npm WARN config production Use
--omit=dev
instead.
adighiero1
TRIALOP

2 years ago

I'm getting this error and even though the page was deployed, it doesn't work. here is the log:

npm WARN config production Use --omit=dev instead.

Jul 29 20:35:31

Jul 29 20:35:31

> ecommerce@1.0.0 start

Jul 29 20:35:31

> node src/app.js --mode produccion

Jul 29 20:35:31

Jul 29 20:35:31

Server listening at Port: 5000

Jul 29 20:35:31

Successfully connected to database

Jul 29 20:35:38

npm WARN config production Use --omit=dev instead.

Jul 29 20:35:38

Jul 29 20:35:38

> ecommerce@1.0.0 start

Jul 29 20:35:38

> node src/app.js --mode produccion

Jul 29 20:35:38

Jul 29 20:35:38

Server listening at Port: 5000

Jul 29 20:35:38

Successfully connected to database

Jul 29 20:35:44

npm WARN config production Use --omit=dev instead.

Jul 29 20:35:44

Jul 29 20:35:44

> ecommerce@1.0.0 start

Jul 29 20:35:44

> node src/app.js --mode produccion

Jul 29 20:35:44

Jul 29 20:35:44

Server listening at Port: 5000

Jul 29 20:35:44

Successfully connected to database

Jul 29 20:35:52

npm WARN config production Use --omit=dev instead.

Jul 29 20:35:52

Jul 29 20:35:52

> ecommerce@1.0.0 start

Jul 29 20:35:52

> node src/app.js --mode produccion

Jul 29 20:35:52

Jul 29 20:35:52

Server listening at Port: 5000

Jul 29 20:35:52

Successfully connected to database

Jul 29 20:35:59

npm WARN config production Use --omit=dev instead.

Jul 29 20:35:59

Jul 29 20:35:59

> ecommerce@1.0.0 start

Jul 29 20:35:59

> node src/app.js --mode produccion

Jul 29 20:35:59

Jul 29 20:35:59

Server listening at Port: 5000

Jul 29 20:35:59

Successfully connected to database

1 Replies

2 years ago

Your logs indicate that the app is running on port 5000, but you have your Railway-generated domain pointing to port 8080.

You can update this by hovering over the domain in the service settings and clicking on the note icon.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...