Releases: effector/next
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
(was22.8.1
)effector-react@22.5.4
(was22.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
v0.2.1
- Fixed typings build
v0.2.0
- Add gip test pages #5 (@AlexandrHoroshih)
- Test app #4 (@AlexandrHoroshih)
🚀 Features
- Minimal effector version is
22.8.1
now #7 (@AlexandrHoroshih)
🐛 Bug Fixes
- Fix missing state ref issues #7 (@AlexandrHoroshih)