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
16
apps/web/next.config.mjs
Normal file
16
apps/web/next.config.mjs
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
import { PHASE_DEVELOPMENT_SERVER } from "next/constants.js";
|
||||
|
||||
/**
|
||||
* Keep dev and production build artifacts separate to avoid chunk/runtime
|
||||
* mismatches when `next dev` and `next build` are run in overlapping sessions.
|
||||
*
|
||||
* @param {string} phase
|
||||
* @returns {import("next").NextConfig}
|
||||
*/
|
||||
export default function nextConfig(phase) {
|
||||
const isDev = phase === PHASE_DEVELOPMENT_SERVER;
|
||||
|
||||
return {
|
||||
distDir: isDev ? ".next-dev" : ".next"
|
||||
};
|
||||
}
|
||||
Loading…
Add table
Add a link
Reference in a new issue