Open Issues Need Help
View All on GitHubLiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: This issue aims to migrate example projects, specifically those using React Native/Expo, from Prettier to Biome to ensure consistent formatting tooling across the monorepo. The primary blocker is Biome's current lack of official support for React Native and Expo, which requires monitoring external development and then verifying compatibility with existing tools like Metro and Expo CLI.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: Enable the `exactOptionalPropertyTypes` TypeScript compiler flag in the LiveStore project to enhance type safety. This involves updating `tsconfig.base.json`, modifying type definitions to explicitly include `| undefined` where necessary, resolving compilation errors, and ensuring test suite success. The task will affect multiple files across various packages within the LiveStore codebase.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: This task involves migrating the `wa-sqlite-build-env` repository into the LiveStore monorepo. This includes moving build scripts, adding `wa-sqlite` as a submodule, updating build processes, extending the `mono` CLI, preserving the Nix setup, and updating documentation. The goal is to improve code sharing, synchronized releases, and simplify development by unifying the two projects.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: The task involves contributing to the LiveStore project, a reactive state management framework. Contributions can range from fixing bugs and improving documentation to developing new features and integrations. The issue outlines several areas needing attention, from maintenance and updates to research and architectural improvements, with specific issues highlighted for easier contribution.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: Implement native support for Effect's `Equal` and `Hash` traits within LiveStore's query system to improve query comparison and caching performance, consistency, and developer experience. This involves optimizing query hashing and equality checks, leveraging Effect's data structures, and integrating with the QueryBuilder for automatic support where schemas are defined. Backward compatibility must be maintained for queries without explicit schemas.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: Enhance LiveStore's state management framework to support schema-first table definitions using the @effect/sql Model integration. This involves modifying the existing `State.SQLite.table()` API to accept Effect Schema definitions, automatically generating column definitions from the schema, and ensuring backward compatibility with the current column-first approach. The goal is to create a single source of truth for table schemas, improve integration with Effect's ecosystem, reduce boilerplate, and enhance type safety.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: Integrate shiki twoslash into the LiveStore documentation build process to enable type checking, enhanced syntax highlighting, and hover information for TypeScript code snippets. This will improve the developer experience and help maintain accurate code examples.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: The task involves making LiveStore's query builder pluggable to support third-party SQLite drivers like Drizzle. This requires investigating compatibility requirements, designing an integration API for external drivers, supporting client-document table creation, and integrating with Effect Schema for type safety. The goal is to allow developers to use their preferred SQLite driver while retaining LiveStore's reactive features and performance.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: The task is to investigate and potentially resolve a warning message related to the `BroadcastChannel` API in the LiveStore Node adapter when used within a Deno environment. The warning indicates that `BroadcastChannel` is unavailable and a fallback is used. The solution might involve either suppressing the warning (if the fallback is sufficient) or exploring ways to enable `BroadcastChannel` support in Deno if truly needed, while considering the unstable flag implications.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: The user is experiencing an issue with the LiveStore devtools in a Vue project using Tailwind CSS. The devtools fail to connect, displaying a session ID of 0. While a workaround involving injecting Tailwind directives into the devtools CSS resolved the styling issue, the connection problem persists. The task is to debug why the LiveStore devtools are failing to establish a connection, even after addressing the styling conflict.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.
AI Summary: The issue describes an error in LiveStore's sync mechanism where, after restarting the server and deleting the `.wrangler/` directory, an invalid parent event number error occurs. The task is to implement a robust error handling mechanism to address this 'Invalid parent event number' error, potentially allowing users to define a fallback strategy or simply providing a clear error report. This involves investigating the synchronization process between the client and server, particularly how event sequencing is managed and how to handle inconsistencies after server restarts or data loss.
LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine.