@tdk-landscape/tdk-cli-core 1.3.59 → 1.3.61

package/CHANGELOG.md

@@ -4,6 +4,14 @@ Notable changes to the `tdk` CLI. Versions match [npm](https://www.npmjs.com/pac
 
 ## Unreleased
 
+- `tdk doctor` and `tdk up` no longer report free host ports (80, 443, 5432) as "taken" on Linux. The port check bound `0.0.0.0` and `127.0.0.1` at the same time, and on Linux the second bind collided with our own first probe. It now probes them one after the other, which still catches a loopback-only Postgres on macOS. Found by the nightly clean-machine quickstart run.
+
+## 1.3.60 (2026-09-27)
+
+- Backends and workers scaffolded by `tdk resource` get a `start` script, and `@types/bun` is pinned instead of `latest`. Before, `tdk doctor` failed on every new service. Found by the clean-machine quickstart run.
+
+## 1.3.59 (2026-09-27)
+
 - `tdk doctor` no longer fails every fresh project with "Generated Dockerfiles reference missing project runtime assets: prisma-runtime-relink.sh, migrate.sh". Those two scripts were never shipped or used by generated Dockerfiles; doctor now checks the scripts TDK ships plus whatever generated Dockerfiles actually copy. Found by the new clean-machine quickstart run.
 
 ## 1.3.58 (2026-09-27)

package/cli/dist/commands/resource.js

@@ -73,6 +73,8 @@ export function createPackageJson(name, type) {
         scripts: {
             dev: isFrontend ? "vite" : "bun run --watch src/index.ts",
             build: isFrontend ? "tsc && vite build" : "tsc",
+            // Backends and workers run `start` in their production image; doctor checks for it.
+            ...(isFrontend ? {} : { start: "bun run dist/index.js" }),
             test: "vitest",
             lint: "biome check .",
             "lint:fix": "biome check . --write",
@@ -81,7 +83,7 @@ export function createPackageJson(name, type) {
             ...(isFrontend ? {} : { hono: "^4.0.0" }),
         },
         devDependencies: {
-            "@types/bun": "latest",
+            "@types/bun": "^1.4.2",
             typescript: "^7.0.2",
             vitest: "^5.0.0",
             "@biomejs/biome": "^2.5.13",

package/cli/dist/utils/doctor-runtime.js

@@ -336,17 +336,18 @@ function probeAddress(port, host) {
     });
 }
 /**
- * Probes both the wildcard and loopback address: a Homebrew Postgres listens on
- * 127.0.0.1 only, which a wildcard bind alone doesn't detect.
+ * Probes both the wildcard and loopback address: on macOS, a Homebrew Postgres
+ * bound to 127.0.0.1 only is invisible to a wildcard-only bind. Sequential, not
+ * concurrent: on Linux, binding 0.0.0.0 and 127.0.0.1 to the same port at the
+ * same time makes the second bind fail with EADDRINUSE against *our own first
+ * probe*, reporting every free port as taken. Binding 0.0.0.0 first and closing
+ * it before trying 127.0.0.1 avoids that self-collision on every platform.
  */
 export async function probeHostPort(port) {
-    const results = await Promise.all([
-        probeAddress(port, "0.0.0.0"),
-        probeAddress(port, "127.0.0.1"),
-    ]);
-    if (results.includes("in-use"))
-        return "in-use";
-    return results.includes("free") ? "free" : "unknown";
+    const wildcard = await probeAddress(port, "0.0.0.0");
+    if (wildcard !== "free")
+        return wildcard;
+    return probeAddress(port, "127.0.0.1");
 }
 /**
  * Catches host ports taken by something other than this project's containers,

package/cli/package.json

@@ -1,7 +1,7 @@
 {
   "name": "tdk-cli-internal",
   "private": true,
-  "version": "1.3.59",
+  "version": "1.3.61",
   "description": "TDK CLI - Tilt Development Kit command line interface",
   "keywords": [
     "tdk",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tdk-landscape/tdk-cli-core",
-  "version": "1.3.59",
+  "version": "1.3.61",
   "description": "Run 100 microservices on a 16 GB laptop without Kubernetes. Scaffold services and run them locally with hot reload, built on Tilt.",
   "homepage": "https://tdk-landscape.github.io/tdk-website",
   "repository": {