fix: allow Renderer class in marked.use

[UziTech]

Marked version: 11.0.0

Description

Ignore extra properties (like options) of classes instead of throwing an error when sending renderer, tokenizer, and hooks to marked.use

Example:

const renderer = new Renderer();
marked.use({ renderer });

Typescript doesn't allow the extra properties and in v11 we throw an error if these properties exist but this will break old extensions. This PR just skips the properties instead of throwing an error.

• Fixes v11.0.0. yields "Uncaught Error: renderer 'options' does not exist" in code that worked in versions up to v10.0.0 #3117

Contributor

• Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
• no tests required for this PR.
• If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

• CI is green (no forced merge required).
• Squash and Merge PR following conventional commit guidelines.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
marked-website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 3, 2023 10:54pm