Where is useBlogPost now? It moves one *more* time?

[li-zhenyu]

Module not found: Error: Can't resolve '@docusaurus/plugin-content-blog/client' in '...'
Docusaurus 3.9.2
An example just like this. When I swizzle BlogPostItem as wrap in Javascript.

import React from 'react';
import BlogPostItem from '@theme-original/BlogPostItem';
import { useBlogPost } from '@docusaurus/plugin-content-blog/client';
const {assets, metadata} = useBlogPost();
const { title, description, date, tags, authors, frontMatter } = metadata;


export default function BlogPostItemWrapper(props) {
  return (
    <>
      <BlogPostItem {...props} />
      <h1>{title}</h1>
    </>
  );
}

[slorber]

It moves one more time?

No need to be condescending 🤷‍♂️

Keep in mind that you deliberately choose to opt-in for implementation detail breaking changes when swizzling a theme compnent flagged as "unsafe", using an api that is not publicly documented: https://docusaurus.io/community/release-process#theming-public-api

That being said, we haven't moved it recently, and the import above should still work. If that's not the case, provide a repro.

[li-zhenyu]

Thanks for reply. The repro has been provided and it simply doesn't work. I encountered this issue when I tried to put a share button on my blog. Basically I understand this is not a bug so I put it here as a discussion. Sorry if my word bother you.

Here are what the Blog page said when I apply my index.js(mentioned above) :

Compiled with problems:
ERROR in ./src/theme/BlogPostItem/index.js 1:80-144
Module not found: Error: Can't resolve '@docusaurus/plugin-content-blog/client' in 'C:\Users\li-zhenyu\Documents\li-zhenyu.github.io\src\theme\BlogPostItem'

Environment: node v24.11.1 on Windows 11 amd64.

Also, is there any publicly available method to obtain BlogPost metadata that can be used? Or are there other recommended way to do that, such as using a preprocessor?

[li-zhenyu]

It should be my own fault because I tried to downgrade docusaurus to 3.5.2 and still not work.

[li-zhenyu]

Surprisingly I find it is beacuse I use pnpm, and I think it has no difference from npm. When I switched to npm, everything works well. Maybe pnpm prevents swizzled components to access internal modules. Now I use npm and everything works well as expected.

[slorber]

afaik pnpm is quite strict in terms of module resolution. You may need to add @docusaurus/plugin-content-blog as a direct dependency of your site

If you use the preset like most sites do, the blog plugin is likely a transitive dependency, and pnpm resolution doesn't see it for your site

[li-zhenyu]

Thank you. It works.