Fix useRemarkSync param type

[karlhorky]

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)
• If applicable, I’ve added docs and tests

Description of changes

It looks like #18 used the UseRemarkOptions type instead of the UseRemarkSyncOptions type for the 2nd parameter of the useRemarkSync() function:

• https://github.com/remarkjs/react-remark/pull/18/files#r1493819195

It seems incorrect to me because of A) the name and B) the onError property not being used.

[ChristianMurphy]

Welcome @karlhorky 👋
I appreciate your enthusiasm and the PR, but also chill.
Multiple passive aggressive @ mentions is a bit much.
It's a type, documentation, I welcome improvements, but is not breaking or a blocker for your usage of the library.
It is also the weekend, take it down a notch.

[ChristianMurphy]

To your CI/CD comment, I think npm has been tested with the legacy version of peer dependencies. The error look like npm's new handling of peer dependencies.
This could either by resolved by adding the legacy peer flag in CI, or focusing on getting #39 wrapped up, which upgrades all the dependencies to newer and more compatible versions.

[karlhorky]

but also chill.

Multiple passive aggressive @ mentions is a bit much

I'm sorry. Was definitely not my intention to cause any stress or be aggressive and I'd like to understand more to improve. I'll try reaching out privately on Twitter/X/email.

[karlhorky]

This could either by resolved by adding the legacy peer flag in CI

Added a step in 0607f10

(Made it a separate step to make it easier to delete later, with less noise in Git blame)

[JounQin]

Glad to see see again @karlhorky!

The changes look good to me.

[ChristianMurphy]

Thanks @karlhorky

[karlhorky]

Glad to help, thanks for the reviews! If there's anything else I should do to get this merged, let me know :)