What is the problem this feature would solve?
Description
After updating Elysia, the startup console log shows:
🔥 Elysia is running at localhost:3000
It would improve developer experience if the full URL including protocol is shown:
🔥 Elysia is running at http://localhost:3000/
Why
- Some terminals allow clickable links only when protocol is included.
- Faster access for developers.
- Consistent with other frameworks (Vite, Next.js, etc).
Suggested change
console.log(🔥 Elysia is running at http://${app.server?.hostname}:${app.server?.port})
Actual Ouptut :

Expected Output :
>
What is the feature you are proposing to solve the problem?
Proposed Feature
Include the protocol (http:// or https://) automatically in the startup log output.
Example:
🔥 Elysia is running at http://localhost:3000/
This could be implemented by:
- Adding protocol detection based on server configuration
- Defaulting to
http:// when TLS is not enabled
- Ensuring the logged URL is directly clickable in terminals
What alternatives have you considered?
Alternatives Considered
- Manually modifying the console log in user code.
- Creating a custom startup logger.
However, including the protocol by default would provide better developer experience out-of-the-box and ensure consistency across projects.
What is the problem this feature would solve?
Description
After updating Elysia, the startup console log shows:
🔥 Elysia is running at localhost:3000
It would improve developer experience if the full URL including protocol is shown:
🔥 Elysia is running at http://localhost:3000/
Why
Suggested change
console.log(
🔥 Elysia is running at http://${app.server?.hostname}:${app.server?.port})Actual Ouptut :

Expected Output :
>
What is the feature you are proposing to solve the problem?
Proposed Feature
Include the protocol (
http://orhttps://) automatically in the startup log output.Example:
🔥 Elysia is running at http://localhost:3000/
This could be implemented by:
http://when TLS is not enabledWhat alternatives have you considered?
Alternatives Considered
However, including the protocol by default would provide better developer experience out-of-the-box and ensure consistency across projects.