[Snyk] Fix for 1 vulnerabilities

[onsails]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-DIFF-14917201	590

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
islamic-website	Error		Jan 25, 2026 9:42am

[Copilot]

Pull request overview

This is a Snyk-generated security fix PR that upgrades react-markdown from 8.0.7 to 9.0.0 and remark-gfm from 3.0.1 to 4.0.0 to address a Regular Expression Denial of Service (ReDoS) vulnerability (SNYK-JS-DIFF-14917201, severity score 590).

Changes:

• Upgraded react-markdown from 8.0.7 to 9.0.0 (major version upgrade)
• Upgraded remark-gfm from 3.0.1 to 4.0.0 (major version upgrade)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Upgrading to react-markdown 9.0.0 introduces breaking changes that will cause build failures. The file src/components/ui/markdown-text.tsx imports types from 'react-markdown/lib/complex-types' (line 5), but this export path no longer exists in react-markdown v9. In v9, types are exported directly from the main package.

Additionally, the component type definitions have changed. The ReactMarkdownProps interface structure and how custom components receive props (including the node property used in the MarkdownHeading component) has been updated in v9.

Before merging this security fix, the code needs to be updated to use the new v9 API. The imports should be changed to import types from 'react-markdown' directly, and the custom component type definitions need to be updated to match the v9 component prop structure.

Suggested change

	"react-markdown": "9.0.0",
	"react-markdown": "8.0.7",