Last 12 weeks · 0 commits
5 of 6 standards met
Please be aware that vibe-coding contributions are 🚫 STRICTLY PROHIBITED. We are humans behind these open source projects, trying hard to maintain good quality and a healthy community. Not only do vibe-coding contributions pollute the code, but they also drain A LOT of unnecessary energy and time from maintainers and toxify the community and collaboration. All vibe-coded, AI-generated PRs will be rejected and closed without further notice. In severe cases, your account might be banned organization-wide and reported to GitHub. PLEASE SHOW SOME RESPECT and do not do so. Before submitting the PR, please make sure you do the following: Read the Contributing Guide. Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate. Provide a description in this PR that addresses what the PR is solving and WHY**, or reference the issue that it solves (e.g. ). Ideally, include relevant tests that fail without this PR but pass with it. [x] Using pnpm patch to fix 's hydration error. I see that the floating-vue repository hasn't accepted any PRs for a long time (the last commit was about two years ago), and I suspect the author of the project no longer maintains it. Therefore, I think the best approach currently is to use pnpm patch to fix this issue with the minimum possible changes.
Please be aware that vibe-coding contributions are 🚫 STRICTLY PROHIBITED. We are humans behind these open source projects, trying hard to maintain good quality and a healthy community. Not only do vibe-coding contributions pollute the code, but they also drain A LOT of unnecessary energy and time from maintainers and toxify the community and collaboration. All vibe-coded, AI-generated PRs will be rejected and closed without further notice. In severe cases, your account might be banned organization-wide and reported to GitHub. PLEASE SHOW SOME RESPECT and do not do so. Before submitting the PR, please make sure you do the following: Read the Contributing Guide. Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate. Provide a description in this PR that addresses what the PR is solving and WHY**, or reference the issue that it solves (e.g. ). Ideally, include relevant tests that fail without this PR but pass with it. [x]
Repository: antfu/nuxt-content-twoslash. Description: TwoSlash integrations for Nuxt Content Stars: 64, Forks: 11. Primary language: TypeScript. Languages: TypeScript (78.8%), JavaScript (21.2%). License: MIT. Latest release: v0.4.0 (3mo ago). Open PRs: 1, open issues: 1. Last activity: 3mo ago. Community health: 85%. Top contributors: antfu, danielroe, onmax, harlan-zw, webdiscus.