Cannot find package 'react-markdown'

[scy6500]

react-markdown version : 7.1.1
react version : rc
next version : 12.0.10
yarn version : 3.1.1

I get an error Cannot find package 'react-markdown' when using react markdown in
next js

Server Error
Error: Cannot find package 'react-markdown' imported from /Users/changyeop/code/{project_name}/.next/server/pages/workspace/view.js
Did you mean to import react-markdown-virtual-2d0e785c49/0/cache/react-markdown-npm-7.1.1-99b3af7151-108759c9e1.zip/node_modules/react-markdown/index.js?

This error happened while generating the page. Any console logs will be displayed in the terminal window.
Call Stack
new NodeError
internal/errors.js (322:7)
packageResolve
internal/modules/esm/resolve.js (732:9)
moduleResolve
internal/modules/esm/resolve.js (773:18)
Loader.defaultResolve [as _resolve]
internal/modules/esm/resolve.js (887:11)
Loader.resolve
internal/modules/esm/loader.js (89:40)
Loader.getModuleJob
internal/modules/esm/loader.js (242:28)
Loader.import
internal/modules/esm/loader.js (177:28)
importModuleDynamically
internal/modules/cjs/loader.js (1028:27)
exports.importModuleDynamicallyCallback
internal/process/esm_loader.js (30:14)
Object.react-markdown
file:///Users/changyeop/code/{project_name}/.next/server/pages/workspace/view.js (318:1)

yarn lock obviously has react-markdown

If i give ssr: false to react-markdown component using next/dynamic, it works well.

// @/components/Markdown
import ReactMarkdown from 'react-markdown';

const MarkdownComponent = ({ text }: any) => {
  return <ReactMarkdown>{text}</ReactMarkdown>;
};
-----------------------------------------------------------
const MarkdownComponent = dynamic(() => import('@/components/Markdown'), {
  ssr: false,
});

Maybe the problem is only with PnP. Has anyone had the same problem?

[ChristianMurphy]

I have not seen that issue before, though PnP has caused a number of similar sounding problems in the past.
Including a reproducible example may help folks offer pointers, for example https://next.new could be used as a starter.
That said, the next.js or yarn teams may be able to offer better guidance, as the issue appears to occur before react-markdown can be loaded or run, in a conflict between yarn and next resolvers.