You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Call for Maintainers: Keeping angular-split future-proof #537
Call for Maintainers: Keeping angular-split future-proof
Hi everyone,
I and @SanderElias had the privilege of maintaining angular-split for some time now. It has been incredibly rewarding to see the library become a staple for split-pane layouts in the Angular community.
As Angular continues to evolve rapidly with new releases, keeping the library compatible, performant, and bug-free is a significant task. To ensure angular-split remains a stable, long-term solution for the ecosystem, we are looking for new maintainers to help steer the project forward
We would like to thank also @Harpush he is a stable factor in het ongoing features/releases off angular-split. He is happy to assist with the new features and the efforts that angular-split needs. And assist you with the maintenance
What does maintenance look like?
The scope is relatively defined, but consistent:
Version Updates: Keeping the library compatible with the latest Angular releases (e.g., ensuring compatibility with current and upcoming Angular versions).
PR Review: Reviewing and merging community contributions, especially those addressing specific CSS/layout bugs or A11y improvements.
Issue Triage: Helping users verify issues and filtering out noise.
Documentation: Keeping the examples and API docs up to date as the framework changes.
Who are we looking for?
You don't need to be the original author to be effective here. If you:
Use angular-split in your professional projects.
Have experience with Angular build tools and package maintenance.
Are committed to keeping the library stable for the community.
...then you are exactly the kind of maintainer we need.
Interested?
If you want to help ensure angular-split stays a reliable resource for everyone, please leave a comment on this issue. I’m happy to discuss the current pipeline and onboarding process.
I would like to step up for this. I am a full stack developer building with Angular and TypeScript daily, with regular open source contributions and maintainer experience behind me; my GitHub profile tells that story better than a list here would.
Rather than only raising my hand, I started with the backlog: #538 brings the toolchain to Angular 22 (building on the groundwork in #531, with a minimal diff on top of current main), handles TypeScript 6 strict defaults properly in the library and demo app, moves CI to Node 22/24, and keeps all 44 Cypress specs green. Next I would take #446 (the gutter ARIA role JAWS bug) and #450 (Cypress tests in TypeScript).
Happy to discuss expectations and process however you prefer.
I see @samuelmbabhazi already stepped up with strong work on Angular 22 (#538). Happy to coordinate so we don't duplicate — if #450 is already in progress on their side I'll pivot to another backlog item (e.g. #446) instead.
Activity
samuelmbabhazi commentedon Aug 18, 2026
Hi @Jefiozie @SanderElias @Harpush,
I would like to step up for this. I am a full stack developer building with Angular and TypeScript daily, with regular open source contributions and maintainer experience behind me; my GitHub profile tells that story better than a list here would.
Rather than only raising my hand, I started with the backlog: #538 brings the toolchain to Angular 22 (building on the groundwork in #531, with a minimal diff on top of current main), handles TypeScript 6 strict defaults properly in the library and demo app, moves CI to Node 22/24, and keeps all 44 Cypress specs green. Next I would take #446 (the gutter ARIA role JAWS bug) and #450 (Cypress tests in TypeScript).
Happy to discuss expectations and process however you prefer.
SkipGip commentedon Oct 27, 2026
Hi @Jefiozie @SanderElias @Harpush,
I'd like to help keep
angular-splitfuture-proof: Angular version bumps, PR review, triage, and docs/examples.I'm @SkipGip (OpenAI Codex for OSS). I use Cursor cloud agents for focused PRs and review everything before it lands.
Upstream PR for #450
I see @samuelmbabhazi already stepped up with strong work on Angular 22 (#538). Happy to coordinate so we don't duplicate — if #450 is already in progress on their side I'll pivot to another backlog item (e.g. #446) instead.