v0.7.2

🐛 Bug Fixes

• Fix custom serialize support for newer effector versions #36 (@AlexandrHoroshih)

v0.7.1

React 19 support

• Extended supported react versions range up to React 19

v0.7.0

🚀 Features

• Support effector 23 #27 (@AlexandrHoroshih)

v0.6.1

🐛 Bug Fixes

• Fix "setState during render" warning #22 (@AlexandrHoroshih)

v0.6.0

@effector/next 0.6.0

Major peer deps update

Minimal required versions of effector and effector-react now are

• effector@22.8.6 (was 22.8.1)
• effector-react@22.5.4 (was 22.5.1)

Fixes

Now all memo(Component) components receive state updates on page transitions correctly

v0.5.0

Changelog

With the recent stabilization of the App Router mode in Next.js 13.4.0, it has now become the primary way to develop Next.js applications.

As a result, we are offering full support for the App Router in @effector/next by injecting the 'use client' directive in the package bundle. We have also updated the documentation to provide more detailed explanations on how to use the App Router with effector.

Pages Router will be supported for a next few major updates of Next.js, so @effector/next still supports it too.

Migration Path

If you previously used @effector/next with App Router by re-exporting the 'provider with 'use client', just use the direct import from the library as the directive is now bundled into the package.
Re-exported version of provider can be deleted from the project.

📚 Pull-requests

• App Router update: Support "use client" #13 (@AlexandrHoroshih)

v0.4.1

🐛 Bug Fixes

• Fix client detection and add tests for that #12 (@AlexandrHoroshih)

v0.4.0

🚀 Features

• Expose getClientScope for dev-tools usage #11 (@AlexandrHoroshih)

v0.3.0

🚀 Features

• Support custom serialize #9 (@AlexandrHoroshih)

🐛 Bug Fixes

• Fix shallow routing edge-cases #10 (@AlexandrHoroshih)

v0.2.2

🐛 Bug Fixes

• Ignore named stores #8 (@zerobias)