Nest: Better getting started developer experience

Created on 23 Jan 2019  路  6Comments  路  Source: nestjs/nest

I'm submitting a...


[ ] Regression 
[ ] Bug report
[ ] Feature request
[x] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior


Currently neither this Introduction page in the doc nor the logs for the apps show the port on which the app is running. I had to dig into the next layer of docs to discover that its localhost:3000. This info isn't self-evident to a new dev & makes for a bewildering initial experience.

Expected behavior


Add app serving address to the Introduction page and to the app logs.

Minimal reproduction of the problem with instructions


Follow installation instructions in the Introduction page.

What is the motivation / use case for changing the behavior?


Better experience for developers new to the framework.

Environment


Nest version: 5.8.0

Most helpful comment

Well, all Node.js developers should know that the default port is 3000.
I do agree, but instead the logger should output which protocol, host and port the server has been started on as well.

All 6 comments

You can just put your port as the first argument when starting the server.

Ah, now I know but the problem still stands, it's still not self-evident to someone new.

Well, all Node.js developers should know that the default port is 3000.
I do agree, but instead the logger should output which protocol, host and port the server has been started on as well.

Coolio.

We are doing our best to make guides as good as possible. Please, give us some time since it costs somewhat effort :)

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings