docs: Update Liveblocks

[matthewlipski]

Pretty self explanatory, just a few questions:

• The example is showing a Duplicate extension names found: ['liveblocksMention'] warning, also with strict mode disabled. Is this smth we need to address? Seems to work well otherwise.
• @nperez0111 when installing @liveblocks/react-blocknote, there was an issue with peer dependencies. Specifically, it needs @blocknote/core: ^0.25.1 but 0.26.0 was provided. This seems like it should be fine as it's not a major version difference so I'm not sure why it's throwing an error. Any ideas why this might be happening? Right now we fixed it with npm install --legacy-peer-deps, but this seems hacky.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
blocknote	✅ Ready (Inspect)	Visit Preview	Apr 3, 2025 1:46pm
blocknote-website	✅ Ready (Inspect)	Visit Preview	Apr 3, 2025 1:46pm

[nperez0111]

• The example is showing a Duplicate extension names found: ['liveblocksMention'] warning, also with strict mode disabled. Is this smth we need to address? Seems to work well otherwise.

I'll take another look at this. Though Tiptap will de-dupe these and only respect one of them (whichever appeared first).

• @nperez0111 when installing @liveblocks/react-blocknote, there was an issue with peer dependencies. Specifically, it needs @blocknote/core: ^0.25.1 but 0.26.0 was provided. This seems like it should be fine as it's not a major version difference so I'm not sure why it's throwing an error. Any ideas why this might be happening? Right now we fixed it with npm install --legacy-peer-deps, but this seems hacky.

So, technically because this is a `0.x` package, that is the correct behavior since in semver `0.x` range is treated specially. I think what liveblocks will need to specify as their peer dep is: `0.25.1 - 1.0.0`

[matthewlipski]

We should probably wait to merge this, since the Liveblocks guys are working on resolving the 2 bullet points in the PR description