Issue with rehype-raw v7.0.0

[lewiswolf]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

8.0.7

Link to runnable example

No response

Steps to reproduce

Update to rehype-raw v7.0.0

Expected behavior

Previous versions did not have this type error.

Actual behavior

error TS2322: Type '(options?: Options | null | undefined) => (tree: Root, file: VFile) => Root' is not assignable to type 'Pluggable<any[]>'.
  Type '(options?: Options | null | undefined) => (tree: Root, file: VFile) => Root' is not assignable to type 'Plugin<any[], any, any>'.
    Type '(tree: Root, file: VFile) => Root' is not assignable to type 'void | Transformer<any, any>'.
      Type '(tree: Root, file: VFile) => Root' is not assignable to type 'Transformer<any, any>'.
        Types of parameters 'file' and 'file' are incompatible.
          Type 'import("/Users/lewiswolstanholme/Desktop/lewiswolstanholme/node_modules/vfile/lib/index").VFile' is not assignable to type 'import("/Users/lewiswolstanholme/Desktop/lewiswolstanholme/node_modules/hast-util-raw/node_modules/vfile/lib/index").VFile'.
            Types of property 'messages' are incompatible.
              Type 'import("/Users/lewiswolstanholme/Desktop/lewiswolstanholme/node_modules/vfile-message/lib/index").VFileMessage[]' is not assignable to type 'import("/Users/lewiswolstanholme/Desktop/lewiswolstanholme/node_modules/hast-util-raw/node_modules/vfile-message/lib/index").VFileMessage[]'.
                Type 'VFileMessage' is missing the following properties from type 'VFileMessage': ancestors, place

rehypePlugins={[rehypeRaw]}

Runtime

No response

Package manager

No response

OS

No response

Build and bundle tools

No response

[ChristianMurphy]

Duplicate of #763 and unifiedjs/unified#228

[github-actions]

Hi! Thanks for taking the time to contribute!

Because we treat issues as our backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn’t an exact duplicate but is closely related.

Thanks,
— bb

[ChristianMurphy]

The type updates are making their way through several hundred packages, for now pin the previous major until the new react-markdown major is released.

[lewiswolf]

sorry for the duplicate! I checked rehype but thought I checked both