Skip to content

PRNext 0.1.19-alpha

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 01 Nov 19:29
0e85ff8

PRNext 0.1.19-alpha is available on npm as an alpha prerelease. Next.js compatibility remains partial; check your application's routes, forms, dependencies and production build before upgrading.

npm install @thomas.f/prnext@0.1.19-alpha

Keep the React protocol packages aligned with the package peer dependencies, then rebuild and restart your application.

The attached archives passed the required CI, six-platform artifact qualification, twelve independent installations, eighteen Node.js lifecycle checks and the controlled performance gate. This does not establish a general speed gain, maximum capacity or absence of memory leaks.

Qualified source: 2346d5cf37f8cd36bf522867b3efcdb61ceadaeb.
Release commit: 0e85ff878132fe0949e749319c4b092d015ffa68.
Read the compatibility guide.

Changes

  • Preserve mounted App layout state when a development Server Action overlaps
    Fast Refresh. Keep unchanged Action identities stable within one development
    session, including Cache Components, while invalidating changed source and
    keeping production build identities independent. Never replay a mutation.
  • Restore the last committed App view before canceling an unfinished streamed
    navigation. Preserve completed Action results, layout state, styles and
    destination history when a newer navigation supersedes its pending render.
  • Detect deep source edits from coalesced macOS directory notifications. Compare
    bounded content snapshots against the compiler's consumed inputs, preserve
    identical generated output and report incomplete coverage explicitly.
  • Follow reachable application and dependency imports in migration checks,
    including conditional exports and the React Server Component import context.
    Report bounded, actionable file/line/import-chain evidence and distinguish
    unknown behavior from checked behavior. Add explicit, application-owned browser
    scenarios for checking both the reference and the candidate server.
  • Keep middleware packages bundled when a native dependency is declared but
    never imported. Follow the resolved dependency graph while preserving
    conservative discovery for computed loads and package-owned native addons.
  • Build Linux standalone deployments with libc and environment detection without
    packaging the build host's ELF/ldd, kernel, cgroup or container probes. Leave
    these exact host resources on the runtime host and preserve tracing-root
    validation for ordinary application files and dependency links.
  • Add opt-in development compilation of literal dynamic client imports with
    experimental.lazyDynamicImports. Compile on first use, retain native ESM
    identity and live bindings, load deferred CSS on activation and preserve Fast
    Refresh state. Activated styles remain loaded for the generation; prefer CSS
    Modules or feature-local selectors. Bound activation queues, generated assets
    and retained registries; reject unsupported configurations explicitly.
  • Preserve query and fragment module identities with their styles in App
    builds. Keep qualified literal imports on the ordinary compiler path and
    reject resolved suffixes that cannot safely reuse deferred export bridges.
  • Add an independently installed SaaS reference using Better Auth, PostgreSQL,
    Drizzle and French/English next-intl routing. Its qualification covers account
    ownership, session renewal/revocation, verified OpenID Connect and a relocated
    two-worker standalone deployment.
  • Add Chromium/Firefox/WebKit compatibility checks, actual production worker
    retirement qualification at the default 30/300-second deadlines, and repeated
    paired archive-to-archive performance comparisons with explicit regression,
    noise and load-generator budgets. Inconclusive evidence is never a pass.
  • Protect pending Flight imports from obsolete HMR generations and preserve
    Server Action errors when navigation replaces their render. Release the
    development commit wait when a newer interaction supersedes that render.
  • Share JSON module identity across deferred importers. Publish complete deferred
    assets exclusively from private staging so a partial write can be retried
    without overwriting immutable assets or losing their quota accounting.
  • Recognize module-level Server Action boundaries in migration import checks.
    Diagnose Node-only imports in client graphs while retaining browser package
    mappings and installed browser implementations.
  • Add shared PostgreSQL authentication budgets to the SaaS reference and qualify
    secure cookies, invalid OIDC callbacks, CSRF, revoked-session mutations and
    relocated standalone authentication through a controlled local HTTPS proxy.
  • Use the unchanged MIT-licensed Node File Trace 1.11.0 distribution with explicit
    patched glob/minimatch dependencies, including independent npm consumers.
  • Retain fine latency histograms and bounded descendant CPU/RSS observations.
    New performance evidence requires verified CPU/memory controls and complete
    measurement coverage. Add scoped diagnostics for development state publication
    failures while retaining the last complete state file. Keep obsolete runtime
    retirement and snapshot retention active when a readiness publication fails,
    while draining existing requests.
  • Share bounded incremental compilation graphs across development projects and
    CSS roles. Preserve lexical build options while canonicalizing graph ownership,
    invalidation and disposal, including macOS system and Windows short-path aliases.
  • Publish affected CSS bundles as small overlays with bounded provenance and
    generation retention. Keep unchanged assets available when another bundle changes.
  • Compile only the deferred client graph for experimental dynamic imports. Validate
    complete asset receipts before publication, retain native module identities and
    reuse existing Server Action proxies without accepting new Action boundaries.
  • Expire idle differential Flight bases automatically and avoid a redundant copy
    for already-owned single cache chunks without exposing mutable producer buffers.
  • Extend migration diagnostics for Redis adapters, server/client directives and
    rendering realms. Detect unsupported .mts/.cts boundaries without executing
    application modules.
  • Honor explicit Link prefetch={true} outside Cache Components. Revalidate the
    destination on click so a prefetch cannot bypass current route authorization.
  • Skip unnecessary Flight indexing for very short initial chunks while preserving
    the exact protocol and fallback. No general HTTP speedup is inferred from the
    focused CPU profile.