You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running serve --no-port-switching with something already on port 3000, serve simply picks another port, ignoring the --no-port-switching flag aimed at forcing the use of a port (#365) .
Running serve --no-port-switching for version 13.0.4 gives the intended behaviour and throws an error: address already in use :::3000 so I think the regression was introduced by the 14.0.0 update.
Library version
14.0.0 and above
Node version
16.18.0
The text was updated successfully, but these errors were encountered:
Description
When running
serve --no-port-switching
with something already on port3000
,serve
simply picks another port, ignoring the--no-port-switching
flag aimed at forcing the use of a port (#365) .Running
serve --no-port-switching
for version13.0.4
gives the intended behaviour and throws an error:address already in use :::3000
so I think the regression was introduced by the14.0.0
update.Library version
14.0.0 and above
Node version
16.18.0
The text was updated successfully, but these errors were encountered: