chore: add github sponsors on supporters by bjohansebas · Pull Request #8531 · nodejs/nodejs.org

bjohansebas · 2026-01-09T17:08:43Z

Description

Note that there’s no REST API for GitHub Sponsors, only a GraphQL API. I’m still working on this.

Preview:

Validation

Related Issues

closes #8199

Check List

I have read the Contributing Guidelines and made commit messages that follow the guideline.
I have run pnpm format to ensure the code follows the style guide.
I have run pnpm test to check if all tests are passing.
I have run pnpm build to check if the website builds without errors.
I've covered new added functionality with unit tests if necessary.

vercel · 2026-01-09T17:08:47Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-org	Ready	Preview	Feb 8, 2026 4:41am

github-actions · 2026-01-09T17:08:53Z

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/nodejs-website

Please review the changes when you have a chance. Thank you! 🙏

github-actions · 2026-01-09T17:16:24Z

📦 Build Size Comparison

Summary

Metric	Value
Old Total Size	3.75 MB
New Total Size	3.75 MB
Delta	0 B (0.00%)

Changes

➕ Added Assets (1)

Name	Size
`.next/static/chunks/bbe6030054b22438.js`	207.00 KB

➖ Removed Assets (1)

Name	Size
`.next/static/chunks/2ad848510aee1f66.js`	207.00 KB

apps/site/next-data/generators/supportersData.mjs

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

bjohansebas · 2026-02-08T04:21:29Z

@nodejs/web-infra I think the new environment variable should also be set in Vercel, since that’s where the website is built, both for production and for previews

apps/site/next-data/generators/supportersData.mjs

+  const mapped = nodes.map(n => {
+    const s = n.sponsor || n.sponsorEntity || n.sponsorEntity; // support different field names
+    return {
+      name: s?.name || s?.login || null,
+      image: s?.avatarUrl || null,
+      url: s?.url || null,
+      source: 'github',
+    };
+  });
+
+  sponsors.push(...mapped);


apps/site/next-data/generators/supportersData.mjs

+  const nodeRes = data.data.organization?.sponsorsActivities;
+
+  const { nodes } = nodeRes;


Copilot

Pull request overview

Adds GitHub Sponsors as an additional data source for the “Supporters” section, alongside OpenCollective, by updating the data generator and wiring the UI/docs to the new combined dataset.

Changes:

Add GitHub Sponsors supporter type and update the Supporters UI to use a unified url field.
Add GitHub GraphQL endpoint constant and implement GitHub Sponsors GraphQL fetching + shuffling in the supporters data generator.
Update partners/supporters copy to mention GitHub Sponsors.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 13 comments.

Show a summary per file

File	Description
apps/site/types/supporters.ts	Introduces a GitHub sponsors supporter type alias.
apps/site/pages/en/about/partners.mdx	Updates “Supporters” copy to include GitHub Sponsors.
apps/site/next.constants.mjs	Adds GitHub GraphQL API endpoint constant.
apps/site/next-data/generators/supportersData.mjs	Expands generator to fetch/merge OpenCollective + GitHub Sponsors and shuffle results.
apps/site/components/Common/Supporters/index.tsx	Updates list rendering to use `url` (and support both sources).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-08T04:26:44Z

apps/site/next-data/generators/supportersData.mjs

+
+  sponsors.push(...mapped);
+
+  return sponsors;


The two GitHub queries (sponsorshipsAsMaintainer and sponsorsActivities) will likely return overlapping sponsors, but the code concatenates both result sets without de-duplication. Consider de-duping by a stable key (e.g., sponsor databaseId/login/url) before shuffling to avoid repeated avatars.

Suggested change

return sponsors;

// De-duplicate sponsors from both queries using a stable key

const seen = new Set();

const uniqueSponsors = [];

for (const sponsor of sponsors) {

const key = sponsor.url || `${sponsor.name || ''}::${sponsor.image || ''}`;

if (seen.has(key)) {

continue;

}

seen.add(key);

uniqueSponsors.push(sponsor);

}

return uniqueSponsors;

hmm, even though it’s a good idea to try to deduplicate it, I don’t think this is the right approach. I’ll have to look into the logic of https://github.com/antfu-collective/sponsorkit33

Copilot · 2026-02-08T04:26:45Z

apps/site/types/supporters.ts

 };

 export type OpenCollectiveSupporter = Supporter<'opencollective'>;
+export type GithubSponsorSupporter = Supporter<'github'>;


Type name uses Github... capitalization. Elsewhere the codebase predominantly uses GitHub (e.g., GitHubApiFile, GitHubIcon). Consider renaming this to GitHubSponsorSupporter for consistency (and update JSDoc imports/usages accordingly).

Suggested change

export type GithubSponsorSupporter = Supporter<'github'>;

export type GitHubSponsorSupporter = Supporter<'github'>;

apps/site/components/Common/Supporters/index.tsx

apps/site/next-data/generators/supportersData.mjs

Copilot · 2026-02-08T04:26:47Z

apps/site/pages/en/about/partners.mdx


 Supporters are individuals and organizations that provide financial support through
-[OpenCollective](https://opencollective.com/nodejs) of the Node.js project.
+[OpenCollective](https://opencollective.com/nodejs) and [GitHub Sponsors](https://github.com/sponsors/nodejs) of the Node.js project.


The sentence reads a bit ungrammatically as written (“through … and … of the Node.js project”). Consider rephrasing to “through … and … for the Node.js project” (or similar) to make the relationship clear.

Copilot · 2026-02-08T04:26:47Z

apps/site/next-data/generators/supportersData.mjs

+const graphql = async (query, variables = {}) => {
+  const res = await fetch(GITHUB_GRAPHQL_URL, {
+    method: 'POST',
+    headers: {
+      'Content-Type': 'application/json',
+      Authorization: `Bearer ${GITHUB_API_KEY}`,
+    },
+    body: JSON.stringify({ query, variables }),
+  });


For consistency/reliability, consider using fetchWithRetry for the GitHub GraphQL POST as well (this file already uses it for OpenCollective). That would reduce transient build/runtime failures due to network timeouts when generating supporters data.

Copilot · 2026-02-08T04:26:47Z

apps/site/next-data/generators/supportersData.mjs

+            sponsorshipsAsMaintainer (first: 100, includePrivate: false, after: "${cursor}", activeOnly: false) {
+                nodes {
+                    sponsor: sponsorEntity {
+                        ...on User {
+                            id: databaseId,
+                            name,
+                            login,
+                            avatarUrl,
+                            url,
+                            websiteUrl
+                        }
+                        ...on Organization {
+                            id: databaseId,
+                            name,
+                            login,
+                            avatarUrl,
+                            url,
+                            websiteUrl
+                        }
+                    },
+                }


The GraphQL query strings contain trailing commas after fields (e.g., id: databaseId,, name,, and a comma after the sponsorEntity { ... } block). GitHub’s GraphQL API does not accept comma-separated field selections, so this query will fail to parse. Remove the commas (and any trailing commas) from the query documents.

apps/site/next-data/generators/supportersData.mjs

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

apps/site/next-data/generators/supportersData.mjs

bjohansebas · 2026-02-08T04:36:22Z

apps/site/next-data/generators/supportersData.mjs

+        organization(login: "nodejs") {
+            sponsorshipsAsMaintainer (first: 100, includePrivate: false, after: "${cursor}", activeOnly: false) {


definitely, I’d prefer that we only show sponsors that are active, but why do we want to show everyone? see #8268.

wdyt @nodejs/nodejs-website @nodejs/marketing ?

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

This comment was marked as off-topic.

Sign in to view

bjohansebas commented Jan 9, 2026

View reviewed changes

apps/site/next-data/generators/supportersData.mjs Show resolved Hide resolved

feat: implement fetch for github sponsors sponsorhip

46d49e7

bjohansebas force-pushed the github_sponsors branch from 06c283f to 46d49e7 Compare January 25, 2026 15:07

vercel bot deployed to Preview January 25, 2026 15:08 View deployment

fixup

00e81c5

vercel bot deployed to Preview February 8, 2026 03:21 View deployment

feat: implement donations queary and fix links

309a8bb

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

vercel bot deployed to Preview February 8, 2026 03:53 View deployment

feat: update text of supporters

70c5076

vercel bot deployed to Preview February 8, 2026 04:01 View deployment

bjohansebas added 2 commits February 8, 2026 04:10

feat: include past sponsors

21655fa

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

feat: sort supporters

448e37e

Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

bjohansebas marked this pull request as ready for review February 8, 2026 04:22

bjohansebas requested a review from a team as a code owner February 8, 2026 04:22

Copilot AI review requested due to automatic review settings February 8, 2026 04:22

Copilot started reviewing on behalf of bjohansebas February 8, 2026 04:22 View session

vercel bot deployed to Preview February 8, 2026 04:23 View deployment

sentry bot reviewed Feb 8, 2026

View reviewed changes

Copilot AI reviewed Feb 8, 2026

View reviewed changes

Update apps/site/next-data/generators/supportersData.mjs

0ad4e41

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

vercel bot deployed to Preview February 8, 2026 04:29 View deployment

sentry bot reviewed Feb 8, 2026

View reviewed changes

apps/site/next-data/generators/supportersData.mjs Show resolved Hide resolved

bjohansebas commented Feb 8, 2026

View reviewed changes

Apply suggestion from @Copilot

6da91ff

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>

vercel bot deployed to Preview February 8, 2026 04:41 View deployment

		const nodeRes = data.data.organization?.sponsorsActivities;

		const { nodes } = nodeRes;

-  return sponsors;
+  // De-duplicate sponsors from both queries using a stable key
+  const seen = new Set();
+  const uniqueSponsors = [];
+  for (const sponsor of sponsors) {
+    const key = sponsor.url || `${sponsor.name || ''}::${sponsor.image || ''}`;
+    if (seen.has(key)) {
+      continue;
+    }
+    seen.add(key);
+    uniqueSponsors.push(sponsor);
+  }
+  return uniqueSponsors;

	export type GithubSponsorSupporter = Supporter<'github'>;
	export type GitHubSponsorSupporter = Supporter<'github'>;

		organization(login: "nodejs") {
		sponsorshipsAsMaintainer (first: 100, includePrivate: false, after: "${cursor}", activeOnly: false) {

Uh oh!

Conversation

bjohansebas commented Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Validation

Related Issues

Check List

Uh oh!

vercel bot commented Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Jan 9, 2026

👋 Codeowner Review Request

Uh oh!

This comment was marked as off-topic.

github-actions bot commented Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📦 Build Size Comparison

Summary

Changes

Uh oh!

Uh oh!

bjohansebas commented Feb 8, 2026

Uh oh!

Uh oh!

This comment was marked as outdated.

Uh oh!

This comment was marked as outdated.

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

bjohansebas Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

bjohansebas Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

bjohansebas Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

bjohansebas commented Jan 9, 2026 •

edited

Loading

vercel bot commented Jan 9, 2026 •

edited

Loading

github-actions bot commented Jan 9, 2026 •

edited

Loading