sindresorhus/get-port

Issues

• Feature Request: function to clear the ports cache

  #57 opened 7 months ago by hasezoey
  4

• Jest tests time out since 5.1.0

  #45 opened a year ago by cegerard
  3

• Portnumber Range Doesnot support in ServerSide

  #67 opened 2 years ago by Sukumaran001
  1

• Error: require() of ES Module not supported

  #66 opened 2 years ago by davidviziteu
  1

• Cannot find module 'node:net' or its corresponding type declarations.

  #65 opened 3 years ago by DoodahProductions
  3

• Fix macOS tests

  #58 opened 3 years ago by sindresorhus
  2

• Possible portNumbers argument validation bug?

  #62 opened 3 years ago by jonahsnider
  3

• Add `exclude` option

  #55 opened 3 years ago by sindresorhus
  1

• (0 , _getPort.portNumbers) is not a function

  #61 opened 3 years ago by YiyuanYin
  1

• Allow a validation function

  #60 opened 3 years ago by Richienb
  3

• ERROR in new Release

  #59 opened 3 years ago by jeanbispo
  1

• Get the port that is not available

  #47 opened 3 years ago by zcmgyu
  1

• Detect docker?

  #9 opened 3 years ago by OmgImAlexis
  11

• Does not assign a random port if the desired port is unavailable

  #31 opened 3 years ago by thomas-alrek
  24

• Feature request: Available port for any localhost host (localhost, 0.0.0.0, 127.0.0.1)

  #48 opened 3 years ago by dylang
  1

• Exclude port option

  #54 opened 3 years ago by vjpr
  1

• Requested port is not assigned after 5.0.0 update, even though its available

  #43 opened 5 years ago by mikemykhaylov
  3

• Get multiple ports via `number` option

  #49 opened 4 years ago by silverwind
  2

• TypeError: interval.unref is not a function

  #44 opened 5 years ago by alexhx5
  0

• Not responding

  #26 opened 5 years ago by Hongdeshuai
  5

• conside provide a synchronous mode options ?

  #41 opened 5 years ago by tjx666
  1

• v4 to v5 Update Functionality Differences

  #34 opened 5 years ago by shellscape
  4

• getPort.makeRange clashing when running parallel tests

  #37 opened 5 years ago by HunorMarton
  2

• Fall back to a random port if prefered port is privileged

  #38 opened 5 years ago by mjgallag
  0

• Is it possible to fix race condition?

  #23 opened 6 years ago by max-block
  5

• Preferred port range?

  #24 opened 6 years ago by tiagosiebler
  10

• Possible interest in hostenv package

  #22 opened 6 years ago by balupton
  4

• Array of preferred ports instead of just one number

  #19 opened 6 years ago by AxelTerizaki
  3

• Race condition

  #14 opened 6 years ago by dotchev
  2

• Default port not catching errors

  #16 opened 7 years ago by reesmanp
  5

• UDP ports do also exist

  #18 opened 7 years ago by ibc
  2

• May I use port range to define preferred port?

  #17 opened 7 years ago by YounGoat
  1

• document that the port may not be immediately available for (re-)use

  #15 opened 7 years ago by tarun
  3

• Node defaults to ipv6 for port resolution

  #8 opened 7 years ago by arcticShadow
  7

• when I listening at 0.0.0.0:8080 , I get port 8080~It's resolve the port is 8080~

  #10 opened 7 years ago by cavacn
  1

• Default port?

  #6 opened 8 years ago by djmadeira
  3

• Allow constraining to a set of possible ports

  #3 opened 9 years ago by callumlocke
  3

• 2.x breaking change could have been avoided

  #1 opened 9 years ago by boneskull
  4