v33.0.0

Breaking Changes

Explicit dependency on @storyblok/react v5

Consumers will already be installing @storyblok/react as a dependency in their own projects, as they need to pass StoryblokComponent into the current StoryblokProvider, so they just need to be sure their dependency is ^5

pnpm i @storyblok/react@5.4.18

Updates Storyblok CLI

You can no longer use v3 of the Storyblok CLI to push the components into your Storyblok space. You must now use v4 of the Storyblok CLI. You can update this by running:

npm install -g storyblok@latest

Remove the StoryblokProvider

We have removed CoralStoryblokProvider from @krakentech/coral-storyblok entirely. This is because we now pass StoryblokComponent or StoryblokServerComponent into our components directly, so there is no need for an additional provider layer.

You can safely remove CoralStoryblokProvider from your app without replacement.

Notes

When passing coralBloks into storyblokInit, consumers can now pass from @krakentech/coral-storyblok/rsc to get the RSC compatible versions.

@krakentech/coral-storyblok and @krakentech/coral-storyblok/client both provide the client component versions.

import { storyblokInit } from "@storyblok/react";
import { coralBloks } from '@krakentech/coral-storyblok';
 
storyblokInit({
  ...
  components: coralBloks
});

import { storyblokInit } from "@storyblok/react";
import { coralBloks } from '@krakentech/coral-storyblok/rsc';
 
storyblokInit({
  ...
  components: coralBloks
});