Skip to content

docs: add sponsors#3674

Open
Shinigami92 wants to merge 4 commits intonextfrom
docs-add-sponsors
Open

docs: add sponsors#3674
Shinigami92 wants to merge 4 commits intonextfrom
docs-add-sponsors

Conversation

@Shinigami92
Copy link
Copy Markdown
Member

@Shinigami92 Shinigami92 commented Dec 18, 2025

Adding a sponsoring section to honor partners.
It is not final yet in which groups we split them.

@Shinigami92 Shinigami92 self-assigned this Dec 18, 2025
@Shinigami92 Shinigami92 added the c: docs Improvements or additions to documentation label Dec 18, 2025
@netlify
Copy link
Copy Markdown

netlify Bot commented Dec 18, 2025

Deploy Preview for fakerjs ready!

Name Link
🔨 Latest commit 7996029
🔍 Latest deploy log https://app.netlify.com/projects/fakerjs/deploys/69ef96272b1a7a000864cf15
😎 Deploy Preview https://deploy-preview-3674.fakerjs.dev
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@codecov
Copy link
Copy Markdown

codecov Bot commented Dec 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.90%. Comparing base (f286dfd) to head (7996029).

Additional details and impacted files
@@           Coverage Diff           @@
##             next    #3674   +/-   ##
=======================================
  Coverage   98.90%   98.90%           
=======================================
  Files         899      899           
  Lines        3113     3113           
  Branches      574      574           
=======================================
  Hits         3079     3079           
  Misses         30       30           
  Partials        4        4           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Shinigami92
Copy link
Copy Markdown
Member Author

Team Decision: @Shinigami92 will try out the https://graphql-docs-v2.opencollective.com/access and dynamically query in vitepress clientside the active sponsors and cache that for ~1 month clientside, so the limit of 10r/min are not exceeded

@Shinigami92 Shinigami92 marked this pull request as ready for review January 9, 2026 11:28
@Shinigami92 Shinigami92 requested a review from a team as a code owner January 9, 2026 11:28
@matthewmayer
Copy link
Copy Markdown
Contributor

I don't see anything new on the deploy preview?

@Shinigami92
Copy link
Copy Markdown
Member Author

I don't see anything new on the deploy preview?

lower right corner

@ST-DDT
Copy link
Copy Markdown
Member

ST-DDT commented Mar 30, 2026

In case this doesn't load, we should handle it more gracefully.

  • maybe silence the error
  • and maybe hide the sponsor header (since it is empty).
empty

Also the initial load looks different than later updates:

Initial After
initial later

(fixes itself on window resize)

Copy link
Copy Markdown
Member

@xDivisionByZerox xDivisionByZerox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good enough for now. We can iterate in the future if we desire to do so.

Copy link
Copy Markdown
Member

@ST-DDT ST-DDT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bug still exists:

Comment on lines +36 to +41
.map((backer) => ({
name: backer.account.name ?? backer.account.slug,
img: backer.account.imageUrl ?? '',
url: `https://opencollective.com/${backer.account.slug}`,
}))
.slice(0, 10) || []
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please filter/reduce the data before writing it to local storage.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I stored the full data on purpose, so if we need to adjust data or want to display more or less later, we don't have a breaking change but just can access the cached data as is.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't expect the used data to change. But 🤷

Comment thread docs/.vitepress/components/AsideSponsors.vue Outdated
backers,
};
} catch {
// Silently ignore fetch errors; the section will hide itself when empty.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe cache the failure, to avoid using up all api limits.

Copy link
Copy Markdown
Member

@ST-DDT ST-DDT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Technically ok, but not really my preference to have.

@ST-DDT ST-DDT added p: 1-normal Nothing urgent do NOT merge yet Do not merge this PR into the target branch yet labels Apr 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

c: docs Improvements or additions to documentation do NOT merge yet Do not merge this PR into the target branch yet p: 1-normal Nothing urgent

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants