chore: upgrade Docusaurus to 3.8 #11260
Conversation
|
Thanks for the PR, @benmccann! 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. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 3a95c2f.
☁️ Nx Cloud last updated this comment at |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11260 +/- ##
=======================================
Coverage 90.91% 90.91%
=======================================
Files 501 501
Lines 50869 50869
Branches 8382 8382
=======================================
Hits 46248 46248
Misses 4606 4606
Partials 15 15
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
fc01c4d to
7d6efcc
Compare
cb427bd to
717bb04
Compare
PR Checklist
Overview
Upgrades from Docusaurus 3.6.1 (what's in the lockfile) to Docusaurus 3.8.1
I have never really used React or Docusaurus, so someone else might have to take this over as it's turned out to be more complicated than I envisioned
The copied over components significantly changed: https://docusaurus.io/blog/releases/3.8#code-block-refactor
I ran
npx docusaurus swizzle @docusaurus/theme-classic CodeBlock/Buttons --ejectand then made a newTryInPlaygroundButtonpulled out from the old code as this new version refactors things to break up the components