Gate live feed staleness and isolate Next dev artifacts
- delay stale status for paused live feeds before surfacing disconnects - keep `next dev` output separate from production build artifacts - add coverage for the new live-feed stale threshold
This commit is contained in:
parent
07a9b91df7
commit
53eeb9e72f
8 changed files with 130 additions and 6 deletions
|
|
@ -1,9 +1,17 @@
|
|||
import { rm } from "node:fs/promises";
|
||||
|
||||
const run = async () => {
|
||||
const port = 3000;
|
||||
const distDir = ".next-dev";
|
||||
console.log(`[web] starting Next.js dev server on port ${port}`);
|
||||
|
||||
const path = Bun.env.PATH ?? "";
|
||||
const cwd = `${import.meta.dir}/..`;
|
||||
const distPath = `${cwd}/${distDir}`;
|
||||
|
||||
// Clear potentially stale dev artifacts from interrupted prior runs.
|
||||
await rm(distPath, { recursive: true, force: true });
|
||||
console.log(`[web] cleared stale Next.js dev artifacts at ${distDir}`);
|
||||
|
||||
const child = Bun.spawn(["next", "dev", "-p", String(port)], {
|
||||
cwd,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue