@zerotal/core 1.1.0 → 1.3.0

package/CHANGELOG.md

@@ -13,7 +13,7 @@ follows the Zerotal monorepo's unified versioning.
 ### Fixed
 
 - **`bun zt test` no longer fails a cold suite on Bun's 5-second hook timeout.** A `beforeAll` that calls `createTestApp()` boots providers and runs migrations, which exceeds 5s on a cold start; `bunfig.toml`'s `[test] timeout` does not cover hooks, only the CLI flag does. The failure appeared on the first run and not the second, which reads as flakiness and sends you looking for a race that is not there. The default is now 30s, still overridable with `--timeout`.
-- **`serve --dev` no longer loses its server to a restart race.** The debounce timer spaced out the *scheduling* of a restart, but its callback cleared the timer and then awaited a rebuild that can take seconds — so a change arriving in that window scheduled a second callback which ran concurrently. Both reached the spawn, two servers raced for the port, and the loser died with "Failed to start server. Is port 3000 in use?". Dev mode was then left owning no server while the winner kept serving stale code, so every later save appeared to do nothing. Restarts are now serialized: a request arriving mid-restart queues exactly one follow-up instead of running in parallel. A failed bind also retries briefly, since the OS releases a listening socket asynchronously after the previous owner exits, and the initial spawn uses the same path — an orphan from a previous run is the commonest reason the first bind fails. An unexpected exit is reported against the child that actually exited rather than whichever child the field happened to hold.
+- **`serve --dev` no longer loses its server to a restart race.** The debounce timer spaced out the _scheduling_ of a restart, but its callback cleared the timer and then awaited a rebuild that can take seconds — so a change arriving in that window scheduled a second callback which ran concurrently. Both reached the spawn, two servers raced for the port, and the loser died with "Failed to start server. Is port 3000 in use?". Dev mode was then left owning no server while the winner kept serving stale code, so every later save appeared to do nothing. Restarts are now serialized: a request arriving mid-restart queues exactly one follow-up instead of running in parallel. A failed bind also retries briefly, since the OS releases a listening socket asynchronously after the previous owner exits, and the initial spawn uses the same path — an orphan from a previous run is the commonest reason the first bind fails. An unexpected exit is reported against the child that actually exited rather than whichever child the field happened to hold.
 
 ### Added
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerotal/core",
-  "version": "1.1.0",
+  "version": "1.3.0",
   "license": "MIT",
   "maturity": "stable",
   "private": false,

package/src/http/index.ts

@@ -30,6 +30,11 @@ export type { UrlGenerator } from "./url.ts";
 export { Http } from "./Http.ts";
 export { UploadedFile } from "./UploadedFile.ts";
 export type { StorageDisk, FileValidationOptions } from "./UploadedFile.ts";
+// Exported for code that must identify bytes it did not receive as an upload —
+// a file fetched from a URL or read back off a disk still needs its type read
+// from its own contents rather than from whatever claimed to describe it.
+export { sniffContentType } from "./sniffContentType.ts";
+export type { SniffedType } from "./sniffContentType.ts";
 export { HttpClientResponse, HttpClientError, PendingRequest } from "./HttpClient.ts";
 export type { FakeStub } from "./HttpClient.ts";
 export { Resource, ResourceCollection } from "./Resource.ts";