I suggest removing getAvailablePort() from @std/net.

Since implementation, Deno.HttpServer.addr.port became available in Deno 1.43. This satisfies the original problem that getAvailablePort() aimed to solve. Example use:

// main.ts
export const port = Deno.serve({ port: 0 }, (_req) => new Response("Hello, world")).addr.port;

// test.ts
import { port } from "./main.ts";
// ...

Secondly, at least according to this GitHub search, it's easily replaced with port: 0 (documentation to be added in denoland/deno#24475).

- import { getAvailablePort } from "@std/net";

Deno.serve({
- port: getAvailablePort(),
  port: 0,
}, (_req) => new Response("Hello, world"));

Lastly, the function is susceptible to a race condition (a port that is deemed available becomes unavailable in between calling getAvailablePort() and the following Deno.serve(), and introduces a dependency when the same functionality is already built into the runtime.

Happy to hear thoughts.

CC @harrysolovay @jollytoad @bcheidemann @dominiq007 (I found your repos used this function)