Unable to pick a custom port for dev mode, yet code exists to do so
See original GitHub issueEnvironment
Nitropack: 0.4.8
Node: 16.11.0
Reproduction
N/A
Describe the bug
As shown at https://github.com/unjs/nitro/blob/main/src/cli.ts#L22 - there is the code avaliable to allow users to pick a custom port/configure the dev server further.
Additional context
We need to pick a port to allow use to debug our serverside while using our frontend on port :3000. We have a specific port we need to pin it on, but we can’t.
Logs
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
node.js - How to make the webpack dev server run on port 80 ...
I have been trying to read the source code in the above repo but failed to find the file which does this setting....
Read more >Development - Parcel
The dev server supports several options, which you can specify via CLI options: -p , --port – Overrides the default port. The PORT...
Read more >Debugging in Visual Studio Code
To run or debug a simple app in VS Code, select Run and Debug on the Debug start view or press F5 and...
Read more >Building applications with Maven - Quarkus
In development mode, Quarkus starts by default with debug mode enabled, listening to port 5005 without suspending the JVM. This behavior can be...
Read more >Opening a port on Linux | DigitalOcean
This can be changed by manually configuring the service to use a different port, but in general, the defaults can be used.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Any news on this @danielroe ?
NITRO_PORT
doesn’t work for me in dev, butPORT
does work.PORT
is already used for many other things and we want to keep dev analogue to prod, where we useNITRO_PORT
. With different env variables, it’s difficult to create a consistent dev experience, especially as there are no cli parameters to specify the port.