Skip to content

Releases: effector/next

v0.7.0

02 Dec 13:03
02a5644
Compare
Choose a tag to compare

🚀 Features

v0.6.1

16 Sep 12:38
77db34c
Compare
Choose a tag to compare

🐛 Bug Fixes

v0.6.0

12 Sep 05:57
0190f41
Compare
Choose a tag to compare

@effector/next 0.6.0

Major peer deps update

Minimal required versions of effector and effector-react now are

Fixes

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

v0.5.0

08 May 12:49
164f9f7
Compare
Choose a tag to compare

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

v0.4.1

07 May 18:06
3611670
Compare
Choose a tag to compare

🐛 Bug Fixes

v0.4.0

06 May 12:08
07608df
Compare
Choose a tag to compare

🚀 Features

v0.3.0

17 Apr 15:23
9f9eef3
Compare
Choose a tag to compare

🚀 Features

🐛 Bug Fixes

v0.2.2

16 Apr 19:34
8ece44a
Compare
Choose a tag to compare

🐛 Bug Fixes

v0.2.1

16 Apr 18:07
Compare
Choose a tag to compare
  • Fixed typings build

v0.2.0

16 Apr 17:51
608334d
Compare
Choose a tag to compare

🚀 Features

🐛 Bug Fixes