@mcrovero/effect-nextjs@0.32.0

Minor Changes

• e041aa4 Thanks @mcrovero! - Require effect >= 3.20.0 and remove the manual Next.js AsyncLocalStorage capture/restore workaround. Request helpers and cache revalidation now rely on Effect's patched async context propagation instead of restoring Next internals explicitly.

Patch Changes

• #57 c53a8a2 Thanks @mcrovero! - Clarify the Next.js request-helper contract in the docs and add regression coverage for readonly headers, cookie mutability, draft mode helpers, and synchronous request-scope errors. Also document that the cache facade currently mirrors the stable cache helpers covered by the repo's tested Next 15.5 setup.

• #56 1fce6e4 Thanks @mcrovero! - Add a real Next.js integration test fixture that exercises the built package in an App Router app, covering request helpers, middleware-provided context, redirects, notFound handling, and route-handler cookie behavior.

• #54 24b167b Thanks @mcrovero! - Fix interrupt-only handler failures so they reject with a real error instead of undefined, and add a regression test for the public Next.build path.

v0.31.0

Minor Changes

• #46 86f98cd Thanks @mcrovero! - Added support for AsyncLocalStorage from Next.js to properly capture and restore context for cache revalidation. The library now imports workAsyncStorage and workUnitAsyncStorage from Next.js internal modules and uses them to maintain context across async boundaries, ensuring proper cache revalidation behavior.

v0.30.0

Minor Changes

• #44 66b4496 Thanks @mcrovero! - Now Nextjs is a peer dependency to be able to use the unstable_throw and effect versions of the Nextjs control-flow redirect, notFound etc.
  Removed runtime registry and related options, you should now only pass stateless Services to Next.

v0.21.0

Minor Changes

• #42 8af5aa5 Thanks @mcrovero! - - feat: Add option to pass a ManagedRuntime using Next.makeWithRuntime(tag, runtime), in addition to the existing Next.make(tag, layer).
  • When a runtime is provided explicitly, it is used as-is and is not registered in the HMR runtime registry; lifecycle is user-managed.
  • breaking: Remove NextMiddleware.layer utility.

v0.20.0

Minor Changes

• #38 b1860e7 Thanks @mcrovero! - ! Breaking: Deprecating NextAction and removed utils to decode params and search params

v0.12.0

Minor Changes

• #36 d6d7633 Thanks @mcrovero! - Added support for Next.js routes. Now Next accepts a list of arguments and middlewares receive props from calling component

v0.11.0

Minor Changes

• #34 04322b2 Thanks @mcrovero! - Moved to a single builder for Pages, Layouts and Server components

v0.10.0

Minor Changes

• #32 e40f93c Thanks @mcrovero! - This version changes the API to use the library, there is no longer a global Next.make(Layer) that exposes .page()/.layout()/.action()/.component() methods. You now need to use: NextPage.make("page_key", Layer), NextLayout.make("layout_key", Layer), etc.
  The keys must be unique across the same type of components.
  There are no more .setParamsSchema(...), .setSearchParamsSchema(...), and .setInputSchema(...).
  You can now use the new helpers inside your handler:

  • yield* Next.decodeParams(schema)(props)
  • yield* Next.decodeSearchParams(schema)(props)

  The actions API has changed, there is no more .build() look at the examples for the new API but .run() waiting to unify the API with the other handlers.

  Read at the bottom of the README for more details for the decisions behind the new API.

v0.6.0

Minor Changes

• 024bdc0 Thanks @mcrovero! - Now uses ManagedRuntime to prevent layers from being provided multiple times

v0.5.0

Minor Changes

• f64d06a Thanks @mcrovero! - Added automatic trace spans and effect stacktrace