Skip to content

feat: add funding.json#1632

Merged
Rich-Harris merged 16 commits intomainfrom
teemingc-patch-1
Feb 27, 2026
Merged

feat: add funding.json#1632
Rich-Harris merged 16 commits intomainfrom
teemingc-patch-1

Conversation

@teemingc
Copy link
Copy Markdown
Member

@teemingc teemingc commented Oct 24, 2025

This PR adds a funding.json file based on https://fundingjson.org which will allow Svelte to apply for funding from https://floss.fund .

The selected projects were based on the search results of FUNDING.yml in our GitHub organisation https://github.com/search?q=org%3Asveltejs%20FUNDING.yml&type=code . But I think there are more projects we could add, just off the top of my head: devalue, svelte-mcp, acorn-ts .

The financial plans are based off the plans in https://opencollective.com/svelte

I chose to omit https://github.com/sponsors/sveltejs as a financial payment method since we don't advertise it anywhere and it looks mostly abandoned. OpenCollective is more transparent anyway.

The annoying bit is that we need to add a .well-known/funding-manifest-urls file to each project's repository if we decide to go ahead with this if we want provenance for those project URLs listed. Once that's done, we can submit the URL to the funding.json file to https://dir.floss.fund/submit to apply

EDIT: removed all projects except svelte and sveltekit so that it's easier for us to get started

Before submitting the PR, please make sure you do the following

  • It's really useful if your PR references an issue where it is discussed ahead of time.
  • Prefix your PR title with feat:, fix:, chore:, or docs:.
  • This message body should clearly illustrate what problems it solves.

Added funding manifest for Svelte, including details about the organization, projects, and funding channels.
@vercel
Copy link
Copy Markdown

vercel Bot commented Oct 24, 2025

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

Project Deployment Actions Updated (UTC)
svelte-dev Ready Ready Preview Feb 27, 2026 7:49pm

Request Review

@teemingc teemingc marked this pull request as draft October 24, 2025 08:58
Comment thread apps/svelte.dev/static/funding.json Outdated
"role": "owner",
"name": "Svelte",
"description": "Web development for the rest of us",
"email": "",
Copy link
Copy Markdown
Member Author

@teemingc teemingc Oct 24, 2025

Choose a reason for hiding this comment

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

We need an official email here so we can be contacted. It's also required by the JSON schema.

@teemingc teemingc marked this pull request as ready for review October 24, 2025 09:13
@teemingc teemingc changed the title chore: add funding.json feat: add funding.json Oct 24, 2025
Comment thread apps/svelte.dev/static/funding.json Outdated
Comment thread apps/svelte.dev/static/funding.json Outdated
Comment thread apps/svelte.dev/static/funding.json Outdated
teemingc and others added 3 commits October 24, 2025 20:06
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
},
"repositoryUrl": {
"url": "https://github.com/sveltejs/svelte",
"wellKnown": "https://github.com/sveltejs/svelte/blob/main/.well-known/funding-manifest-urls"
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.

Note that a file similar to https://github.com/sveltejs/svelte.dev/pull/1632/files#diff-dc6aa312408365efda3e35f463314bc3c7a2f37df864885c94ab21be318e8f6c needs to be added to the Svelte repository to provide provenance to the manifest.

Copy link
Copy Markdown
Member Author

@teemingc teemingc Feb 27, 2026

Choose a reason for hiding this comment

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

},
"repositoryUrl": {
"url": "https://github.com/sveltejs/kit",
"wellKnown": "https://github.com/sveltejs/kit/blob/main/.well-known/funding-manifest-urls"
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.

Note that a file similar to https://github.com/sveltejs/svelte.dev/pull/1632/files#diff-dc6aa312408365efda3e35f463314bc3c7a2f37df864885c94ab21be318e8f6c needs to be added to the SvelteKit repository to provide provenance to the manifest.

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.

Comment thread apps/svelte.dev/static/funding.json Outdated
Comment thread apps/svelte.dev/static/funding.json Outdated
@Rich-Harris Rich-Harris merged commit eaff956 into main Feb 27, 2026
1 of 2 checks passed
@Rich-Harris Rich-Harris deleted the teemingc-patch-1 branch February 27, 2026 19:48
Rich-Harris pushed a commit to sveltejs/svelte that referenced this pull request Feb 27, 2026
Related to sveltejs/svelte.dev#1632

This will allow us to apply for a grant from floss.fund

### Before submitting the PR, please make sure you do the following

- [ ] It's really useful if your PR references an issue where it is
discussed ahead of time. In many cases, features are absent for a
reason. For large changes, please create an RFC:
https://github.com/sveltejs/rfcs
- [ ] Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`.
- [ ] This message body should clearly illustrate what problems it
solves.
- [ ] Ideally, include a test that fails without this PR but passes with
it.
- [ ] If this PR changes code within `packages/svelte/src`, add a
changeset (`npx changeset`).

### Tests and linting

- [ ] Run the tests with `pnpm test` and lint the project with `pnpm
lint`
Rich-Harris pushed a commit to sveltejs/kit that referenced this pull request Feb 27, 2026
Related to sveltejs/svelte.dev#1632

This will allow us to apply for a grant from floss.fund

---

### Please don't delete this checklist! Before submitting the PR, please
make sure you do the following:
- [ ] It's really useful if your PR references an issue where it is
discussed ahead of time. In many cases, features are absent for a
reason. For large changes, please create an RFC:
https://github.com/sveltejs/rfcs
- [ ] This message body should clearly illustrate what problems it
solves.
- [ ] Ideally, include a test that fails without this PR but passes with
it.

### Tests
- [ ] Run the tests with `pnpm test` and lint the project with `pnpm
lint` and `pnpm check`

### Changesets
- [ ] If your PR makes a change that should be noted in one or more
packages' changelogs, generate a changeset by running `pnpm changeset`
and following the prompts. Changesets that add features should be
`minor` and those that fix bugs should be `patch`. Please prefix
changeset messages with `feat:`, `fix:`, or `chore:`.

### Edits

- [ ] Please ensure that 'Allow edits from maintainers' is checked. PRs
without this option may be closed.
Copilot AI pushed a commit to Stadly/kit that referenced this pull request Mar 6, 2026
Related to sveltejs/svelte.dev#1632

This will allow us to apply for a grant from floss.fund

---

### Please don't delete this checklist! Before submitting the PR, please
make sure you do the following:
- [ ] It's really useful if your PR references an issue where it is
discussed ahead of time. In many cases, features are absent for a
reason. For large changes, please create an RFC:
https://github.com/sveltejs/rfcs
- [ ] This message body should clearly illustrate what problems it
solves.
- [ ] Ideally, include a test that fails without this PR but passes with
it.

### Tests
- [ ] Run the tests with `pnpm test` and lint the project with `pnpm
lint` and `pnpm check`

### Changesets
- [ ] If your PR makes a change that should be noted in one or more
packages' changelogs, generate a changeset by running `pnpm changeset`
and following the prompts. Changesets that add features should be
`minor` and those that fix bugs should be `patch`. Please prefix
changeset messages with `feat:`, `fix:`, or `chore:`.

### Edits

- [ ] Please ensure that 'Allow edits from maintainers' is checked. PRs
without this option may be closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants