Releases: evoluhq/evolu
evolu-server@1.0.4
evolu@6.0.2
Patch Changes
- f585bd4: Change SQLite dependency from peer to normal
evolu@6.0.1
Patch Changes
- 182bd28: A fix for React Server Components in Next.js App Router
evolu@6.0.0
Major Changes
-
c7f5182: React Suspense
It's about time. React Suspense is an excellent React feature that massively improves both UX and DX. It's a breaking change because I decided to remove the
isLoadingandisLoadedstates entirely. It's not necessary anymore. Use React Suspense.Implementing and testing React Suspense also led to internal optimizations for faster and more reliable syncing and better unit tests.
This release also includes SQLite 3.42.0. There is no breaking change in data persistence.
evolu-server@1.0.3
Patch Changes
- Updated dependencies [f585bd4]
- evolu@6.0.2
evolu-server@1.0.2
Patch Changes
- Updated dependencies [182bd28]
- evolu@6.0.1
evolu-server@1.0.1
Patch Changes
- Updated dependencies [c7f5182]
- evolu@6.0.0
evolu@5.0.0
Major Changes
-
590d5a8: Port Evolu from fp-ts to Effect
Nothing changed except Evolu is internally using Effect instead of fp-ts now. Because of that, I refactored all source code hence a major change.
Effect is the successor of fp-ts. If you already know fp-ts, you will understand it quickly. If you don't know fp-ts yet, skip it, and learn Effect instead. Give it five minutes, and you will love it.
The devil's advocate question: Could Evolu be written without Effect? It could be, but the source code would be uglier, brittle, and slower. Let me explain it. For now, Evolu is using a synchronous version of SQLite. But soon, we will also use asynchronous SQLite for other platforms where synchronous SQLite is not available. With Effect, the code is the same. Without Effect, we would always use Promises, even for synchronous code. Or we would have to write the same logic twice. As for brittle code, Effect catches and can recover from all errors. As for uglier code, errors we can expect are typed. And much more. I believe Effect will be the next big thing in the JavaScript ecosystem.
evolu-server@1.0.0
Major Changes
-
590d5a8: Port Evolu from fp-ts to Effect
Nothing changed except Evolu is internally using Effect instead of fp-ts now. Because of that, I refactored all source code hence a major change.
Effect is the successor of fp-ts. If you already know fp-ts, you will understand it quickly. If you don't know fp-ts yet, skip it, and learn Effect instead. Give it five minutes, and you will love it.
The devil's advocate question: Could Evolu be written without Effect? It could be, but the source code would be uglier, brittle, and slower. Let me explain it. For now, Evolu is using a synchronous version of SQLite. But soon, we will also use asynchronous SQLite for other platforms where synchronous SQLite is not available. With Effect, the code is the same. Without Effect, we would always use Promises, even for synchronous code. Or we would have to write the same logic twice. As for brittle code, Effect catches and can recover from all errors. As for uglier code, errors we can expect are typed. And much more. I believe Effect will be the next big thing in the JavaScript ecosystem.
Patch Changes
- Updated dependencies [590d5a8]
- evolu@5.0.0
evolu@4.1.2
Patch Changes
- 3140595: Update dependencies