Skip to content

Releases: fridge-cms/fridge.js

7.0.0

03 Jan 17:28
ca31d0c
Compare
Choose a tag to compare
  • Moved next to a peerDependency so we don't need to keep re-releasing to update the version of next.
  • Switched to using a next plugin so that this will interop with a regular next.js app.
  • Rewrite server bits to use fastify and compression.
  • Temporarily disable ssr caching until a better solution is found.
  • Test custom routes, exportPathMap, and now v2 custom routes

4.2.0

13 Jun 13:55
Compare
Choose a tag to compare
  • Introduced dynamic routing via routes config option. It is an object in the format of {path: page}. Any named parameters in the path string get passed as query params to the page.

4.0

16 May 15:01
Compare
Choose a tag to compare
4.0
  • Upgraded to next.js 6.0
  • Reorganize modules and names for easier setup
  • Added <Fridge> component and <HtmlContent> component

Breaking Changes

We no longer include an HOC to wrap top-level pages. The custom <App> functionality introduced by next.js 6.0 drastically reduces the amount of cruft we need to write in our page components, so we now provide a FridgeApp to set everything up for you.

connectFridge has been renamed to withFridge. It's shorter, and makes more sense.

3.0

16 May 14:58
Compare
Choose a tag to compare
3.0
  • Uses new Fridge v2 API

v2.0

10 Jan 18:03
Compare
Choose a tag to compare
  • Improved data-fetching to work client-side and with HMR

Initial Release

08 Jan 17:24
Compare
Choose a tag to compare
fix exporting issue. properly set FRIDGE_SECRET to empty string if it is

not present in config