feat(plugin-npm2yarn): Add Bun to default tabs conversions

[jakeboone02]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.

Motivation

Bun is mentioned as being one of the default converters in packages/docusaurus-remark-plugin-npm2yarn/README.md, but it wasn't actually implemented as a default in packages/docusaurus-remark-plugin-npm2yarn/src/index.ts.

Bun is probably popular enough by now that it warrants inclusion as a default.

I also updated the README for the package to show the default converters as an actual array value and updated the example screenshot with pnpm and Bun.

Test Plan

Updated packages/docusaurus-remark-plugin-npm2yarn/src/__tests__/__snapshots__/index.test.ts.snap.

I wasn't able to run the tests locally, so I updated the snapshot manually for the first commit. I can fix the snapshot if the tests fail in CI. Fixed.

Test links

Deploy preview: https://deploy-preview-10953--docusaurus-2.netlify.app/docs/installation/#build

Related issues/PRs

• fix(npm-to-yarn): add missing npm-to-yarn converter for Bun #10803

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	95af630
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/67cf084f951d48000803c146
😎 Deploy Preview	https://deploy-preview-10953--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	Report
/	🟠 61	🟢 98	🟢 96	🟢 100	Report
/docs/installation	🔴 47	🟢 97	🟢 100	🟢 100	Report
/docs/category/getting-started	🟠 73	🟢 100	🟢 100	🟠 86	Report
/blog	🟠 63	🟢 96	🟢 100	🟠 86	Report
/blog/preparing-your-site-for-docusaurus-v3	🟠 65	🟢 92	🟢 100	🟢 100	Report
/blog/tags/release	🟠 63	🟢 96	🟢 100	🟠 86	Report
/blog/tags	🟠 69	🟢 100	🟢 100	🟠 86	Report

[slorber]

Thanks

Ok to do that but I'm going to consider it a feat, not a fix.

It's a behavior change that users upgrading must be aware of, and documented properly in our release notes.

I even wonder if we shouldn't keep it for v4 (soon), because it's not critical and may annoy some users upgrading that would now need to disable this conversion. See for example: electron/website#421

Any thought @Josh-Cena ?

[jakeboone02]

Yeah, good points. I debated prefixing the PR description with "fix" vs "feat", and only went with "fix" because the README conflicted with the actual behavior.

A major version bump would be a good time to make the change.

[slorber]

Yeah, let's delay this to v4, it's safer, not too far, and there's a good enough workaround until then.

[Josh-Cena]

I don't have thoughts wrt to v3 or v4. I don't think it's major enough, actually—it's a normal feature enhancement. I don't really know what users expect when they use this feature though.

[jakeboone02]

I don't have strong feelings about it either, but FWIW as a user of the feature I would assume the default meant "show all the reasonably popular ones" (which includes Bun at this point). I doubt many people would assume the default meant "show all the popular ones as of the last major version bump of this Docusaurus plugin," and anyone needing to customize the list would have already done that anyway.

[slorber]

Ok let's merge this for v3.8 then 👍 It's easy to revert if needed and shouldn't really harm anyone

[Josh-Cena]

It's customizable anyway—we just need to point to the option to restore previous behavior in the release notes