A collection of standalone tools and libraries to accelerate SvelteKit and GraphQL web application development.
KitQL is a collection of standalone libraries and tools designed to speed up the development of web applications, especially those using SvelteKit and GraphQL. It provides utilities for type-safe routing, automated task execution, GraphQL helpers, and code quality enforcement, solving common development bottlenecks and reducing boilerplate.
Web developers and teams building applications with SvelteKit and GraphQL who want to improve development speed, maintain type safety, and adopt best practices with minimal configuration.
Developers choose KitQL for its modular, focused tools that integrate seamlessly into existing workflows, offering immediate productivity gains without the overhead of a full framework. Its standalone nature allows selective adoption, and its strong emphasis on type safety and automation reduces errors and accelerates iteration.
A set of standalone tools to SpeedRun WebApps!
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
vite-plugin-kit-routes generates type-safe route helpers for SvelteKit, eliminating broken links and improving code reliability through automated type generation.
vite-plugin-watch-and-run automatically executes commands on file changes, streamlining workflows like code generation and reducing manual intervention during development.
Each library is standalone, allowing developers to adopt only needed tools—such as @kitql/eslint-config for linting or vite-plugin-stripper for optimization—without framework bloat.
Provides dedicated helpers like @kitql/helpers for GraphQL schema and operation management, enhancing productivity in GraphQL-based SvelteKit applications.
Setting up multiple Vite plugins and libraries requires manual integration in SvelteKit projects, which can be complex and error-prone compared to unified solutions.
Heavy focus on GraphQL tooling means limited value for projects using REST or alternative APIs, restricting its applicability to specific tech stacks.
Documentation is spread across individual package READMEs, making it challenging to get a cohesive overview and increasing the learning curve for new users.