Svelte is a new way to build web applications. It's a compiler that takes your declarative components and converts them into efficient JavaScript that surgically updates the DOM.
The Open Source Guides website has a collection of resources for individuals, communities, and companies. These resources help people who want to learn how to run and contribute to open source projects. Contributors and people new to open source alike will find the following guides especially useful:
There are many ways to contribute to Svelte, and many of them do not involve writing any code. Here's a few ideas to get started:
- Simply start using Svelte. Go through the Getting Started guide. Does everything work as expected? If not, we're always looking for improvements. Let us know by opening an issue.
- Look through the open issues. A good starting point would be issues tagged good first issue. Provide workarounds, ask for clarification, or suggest labels. Help triage issues.
- If you find an issue you would like to fix, open a pull request.
- Read through our tutorials. If you find anything that is confusing or can be improved, you can make edits by clicking "Edit this page" at the bottom left of the tutorial page.
- Take a look at the features requested by others in the community and consider opening a pull request if you see something you want to work on.
Contributions are very welcome. If you think you need help planning your contribution, please ping us on Discord at svelte.dev/chat and let us know you are looking for a bit of help.
One great way you can contribute to the project without writing any code is to help triage issues and pull requests as they come in.
- Ask for more information if you believe the issue does not provide all the details required to solve it.
- Flag issues that are stale or that should be closed.
- Ask for test plans and review code.
If you'd like to propose an implementation for a large new feature or change then please create an RFC to discuss it up front.
When deciding where to contribute, you may wish to take a look at our roadmap. The Svelte team generally works on a single major effort at a time. This has a couple benefits for us as maintainers. First, it allows us to focus and make noticeable progress in an area being proactive rather than reactive. Secondly, it allows us to handle related issues and PRs together. By batching issues and PRs together we’re able to ensure implementations and fixes holistically address the set of problems and use cases encountered by our users.
The maintainers meet on the final Saturday of each month. While these meetings are not open publicly, we will report back by leaving a comment on each issue discussed. We will generally discuss items aligning with our roadmap, but major PRs needing discussion amongst the maintainers can be added to the agenda for the monthly maintainer’s meeting. However, we typically are only able to get to a couple of items that are not aligned with our current priority.
We do our best to review PRs and RFCs as they are sent, but it is difficult to keep up. We welcome help in reviewing PRs, RFC, and issues. If an item aligns with the current priority on our roadmap, it is more likely to be reviewed quickly. PRs to the most important and active ones repositories get reviewed more quickly while PRs to smaller inactive repos may sit for a bit before we periodically come by and review the pending PRs in a batch.
We use GitHub issues for our public bugs. If you would like to report a problem, take a look around and see if someone already opened an issue about it. If you are certain this is a new unreported bug, you can submit a bug report.
If you have questions about using Svelte, contact us on Discord at svelte.dev/chat, and we will do our best to answer your questions.
If you see anything you'd like to be implemented, create a feature request issue
When opening a new issue, always make sure to fill out the issue template. This step is very important! Not doing so may result in your issue not being managed in a timely fashion. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.
- One issue, one bug: Please report a single bug per issue.
- Provide reproduction steps: List all the steps necessary to reproduce the issue. The person reading your bug report should be able to follow these steps to reproduce your issue with minimal effort. If possible, use the REPL to create your reproduction.
HEADS UP: Svelte 5 will likely change a lot on the compiler. For that reason, please don't open PRs that are large in scope, touch more than a couple of files etc. In other words, bug fixes are fine, but big feature PRs will likely not be merged.
If you would like to request a new feature or enhancement but are not yet thinking about opening a pull request, you can also file an issue with feature template.
If you're only fixing a bug, it's fine to submit a pull request right away, but we still recommend that you file an issue detailing what you're fixing. This is helpful in case we don't accept that specific fix but want to keep track of the issue.
Small pull requests are much easier to review and more likely to get merged.
- Ensure you have pnpm installed
- After cloning the repository, run
pnpm install. You can do this in the root directory or in thesvelteproject - Move into the
sveltedirectory withcd packages/svelte - To compile in watch mode, run
pnpm dev
Fork the repository and create your branch from master. If you've never sent a GitHub pull request before, you can learn how from this free video series.
A good test plan has the exact commands you ran and their output, provides screenshots or videos if the pull request changes UI.
- If you've changed APIs, update the documentation.
All tests are located in /test folder.
Test samples are kept in /test/xxx/samples folder.
PREREQUISITE: Install chromium via playwright by running
pnpm playwright install chromium
- To run test, run
pnpm test. - To run test for a specific feature, you can use the
-g(aka--grep) option. For example, to only run test involving transitions, runpnpm test -- -g transition.
- To run only one test, rename the test sample folder to end with
.solo. For example, to run thetest/js/samples/actiononly, rename it totest/js/samples/action.solo. - To run only one test suite, rename the test suite folder to end with
.solo. For example, to run thetest/jstest suite only, rename it totest/js.solo. - Remember to rename the test folder back. The CI will fail if there's a solo test.
- Tests suites like
css,js,server-side-renderingasserts that the generated output has to match the content in the.expectedfile. For example, in thejstest suites, the generated js code is compared against the content inexpected.js. - To update the content of the
.expectedfile, run the test with--updateflag. (pnpm test --update)
Eslint will catch most styling issues that may exist in your code. You can check the status of your code styling by simply running pnpm lint.
snake_casefor internal variable names and methods.camelCasefor public variable names and methods.
Please make sure the following is done when submitting a pull request:
- Describe your test plan in your pull request description. Make sure to test your changes.
- Make sure your code lints (
pnpm lint). - Make sure your tests pass (
pnpm test).
All pull requests should be opened against the master branch. Make sure the PR does only one thing, otherwise please split it.
When adding a new breaking change, follow this template in your pull request:
### New breaking change here
- **Who does this affect**:
- **How to migrate**:
- **Why make this breaking change**:
- **Severity (number of people affected x effort)**:By contributing to Svelte, you agree that your contributions will be licensed under its MIT license.
Feel free to ask in #contributing on Discord if you have questions about our process, how to proceed, etc.