fix: enhance img component className handling

[dborysov]

No description provided.

[netlify]

✅ Deploy Preview for tanstack ready!

Name	Link
🔨 Latest commit	d7e9492
🔍 Latest deploy log	https://app.netlify.com/projects/tanstack/deploys/689a224c6994c2000833d165
😎 Deploy Preview	https://deploy-preview-462--tanstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 29 (🔴 down 3 from production) Accessibility: 98 (no change from production) Best Practices: 83 (no change from production) SEO: 95 (no change from production) PWA: 60 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull Request Overview

This PR enhances the img component in the Markdown component to properly handle className props by merging them with default styling classes.

• Modified the img component to accept and merge additional className props with existing default styles

[Copilot]

[nitpick] The template literal with line breaks makes the className construction harder to read and maintain. Consider using a utility function like clsx or cn for cleaner class merging, or format it as a single line.

[SeanCassiere]

Was there anywhere where this specifically affected the content on the website?

[dborysov]

Was there anywhere where this specifically affected the content on the website?

Yes, here the browsers´ logos are not properly styled - should be inlined (like here)

I searched other places and <img> is only used in a couple of README files, where class is not used. Can you think about any cases where this change can be dangerous?

[SeanCassiere]

Thanks!