Status Update - May 2026 · Issue #4707 · leptos-rs/leptos · GitHub
//voltron/issues_fragments/issue_layout" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
//voltron/issues_fragments/issue_layout;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
leptos-rs
leptos
Public
Uh oh!
There was an error while loading. Please reload this page.
Notifications<br>You must be signed in to change notification settings
Fork<br>868
Star<br>20.8k
Status Update - May 2026 #4707
New issue<br>Copy link
New issue<br>Copy link
Open
Open<br>Status Update - May 2026#4707
Copy link
Description
gbj<br>opened on May 8, 2026
Issue body actions
I wanted to provide a short update on the current state of Leptos development, so that people have an accurate understanding of where things are currently.
tl:dr; Leptos is not abandoned but will be lightly maintained going forward. I consider it feature-complete and do not expect to do significant new development in the future. I am open to additional maintainers who want to take a more active role.
Background
I created Leptos as an experiment and personal project, at a time when I was learning Rust and was very interested in using it for web applications. It's been successful for that purpose! It's also been much more popular than I would have expected at that time, in part thanks to the publicity it received very early on from several developers with very large online followings.
Working on an open source project that has users is fulfilling, but it can also be draining over time. It's fun to interact with people, but it's tiring to answer the same questions year after year. It's interesting to work on new features and solve big problems, but—especially once a project has reached maturity—it's exhausting to deal with dozens of niche issues.
The rise of LLMs and of coding agents has really fundamentally changed the cost-benefit analysis on this for me. Over the last year or so I've found that the volume of meaningful community conversation and engagement has declined significantly. Over the last few weeks I've experienced a new and sad problem first-hand: the replacement of human-to-human conversation over issues and PRs with replies directly copied-and-pasted from an agent, formatting and all.
I am lucky enough not to make a living in the tech industry, so I am insulated from some of these changes in my day to day. Leptos is and has always been a passion project for me; I am grateful for the support of many others along the way, but it's time for me to take a bit of a step back.
The Present
I consider Leptos complete. I have shipped every major feature on any of my roadmaps.
On the final roadmap post, you can see a number of disparate feature requests from members of the community. Some of these are best developed in the community (like a component library or other approaches to routing). Others are beyond the scope of my work ("can you implemented this React feature?") Leptos currently supports everything I have ever wanted it to do. I'm happy with the work.
There has been some ongoing, slow work on a leptos_0.9 branch, which includes some cleanup and fixes that require a semver-breaking release. At this point, I'd love some help reviewing any additional PRs that should be merged into that branch, and fixing any remaining issues in that milestone, while building toward a release. I don't feel much urgency about it, and it doesn't contain any significant new features.
The Future
I'm not planning to abandon the project. I'm also not planning on any big new feature pushes.
I'm very open to anyone who wants to help maintain the project in an active way. I'm likely going to engage a little less with issues/discussions/PRs than I have historically, but I still get all the same notifications.
At this point, it's primarily a question of where and how I want to invest my time and attention in the years ahead. If it's important to you that someone be actively working on fixing the sorts of bugs that are currently in the issue tracker, or implementing the kinds of feature requests that are currently open—reach out and let me know! I'd be very happy to help onboard anyone to the codebase who wants to help maintain it.
Reactions are...