chore(website): auto-inject ban-types default options

[Josh-Cena]

PR Checklist

• Addresses an existing open issue: fixes Docs: ban-types.md should pull in defaultTypes automatically #6210
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

Ideally I should use an actual parser to get the defaultTypes, but there's no parser package readily installed in the website, so I thought this should do too.

[typescript-eslint]

Thanks for the PR, @Josh-Cena!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

---

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	3427afb
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/653162bd25cd9c0008f7ef4a
😎 Deploy Preview	https://deploy-preview-7714--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 95 (no change from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

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

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 3427afb. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 19 targets

• nx test eslint-plugin --coverage=false
• nx test visitor-keys --coverage=false
• nx run types:build
• nx run repo-tools:postinstall-script
• nx test scope-manager --coverage=false
• nx test utils --coverage=false
• nx test rule-schema-to-typescript-types --coverage=false
• nx test type-utils --coverage=false
• nx test typescript-estree --coverage=false
• nx test eslint-plugin-tslint --coverage=false
• nx test parser --coverage=false
• nx test repo-tools --coverage=false
• nx test eslint-plugin-internal --coverage=false
• nx test ast-spec --coverage=false
• nx run-many --target=typecheck --parallel
• nx run-many --target=lint --parallel
• nx run eslint-plugin:generate:configs
• nx run integration-tests:test
• nx run-many --target=build --parallel --exclude=website --exclude=website-eslint

---

Sent with 💌 from NxCloud.

[JoshuaKGoldberg]

😬 I do dislike having such rule-specific things in this already kind of big file... what do you think about having an mdx component like <BanTypesDefaultOptions />?

[Josh-Cena]

We already have file-specific handling for this page. This cannot be an MDX component because it has to work server-side and get statically injected instead of dynamically rendered.

[JoshuaKGoldberg]

Blurgh, I keep forgetting these things. MDX components don't work server-side? Is this mentioned in docs / one of the things blocked by MDX v2? (I searched and can't find it)

[Josh-Cena]

MDX components are basically React components. They can get server-rendered (through the same machinery that renders the rest of the page to HTML) but they can't access server data like files.

[JoshuaKGoldberg]

Seems reasonable - I'll defer to you on Docusaurus things 😄