Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Drop postgres requirement for easier adoption

未关闭
  • 哪里不对？
#203 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
bun, postgresql, sqlite, typescript
领域
database

调研方向

Start with the existing Postgres adapter and the storageContract tests, then review how Bun's SQL handles SQLite transactions. Add a SQLite storage adapter for single-user use and ensure concurrent transactions are handled one at a time. Done means the adapter passes storageContract alongside the existing adapters.

由索引模型根据 Issue 内容生成。

描述

enhancement triage/human-response

Awesome project! While it's in early stages I think this project is most likely to be used single player. With that said making a sqlite adapter I think would be worthwhile.

here's a rough plan from claude

Add a SQLite storage adapter for single-user local use. It seems to fit
the current design:

  • One process already owns writes (the writer lease plus the global advisory
    lock), which is SQLite's normal mode.
  • The Postgres adapter uses Bun's SQL, which also accepts sqlite:// URLs.
    RETURNING, ON CONFLICT, JSON functions and BLOBs work there.
  • storageContract already runs against two adapters, so a third could be
    proven against it.

The main gotcha: Bun's SQLite mode doesn't queue concurrent sql.begin()
calls, so the adapter would need to run transactions one at a time. With a
simple promise queue, 20 concurrent transactions all succeeded; without it,
19 failed.

主要语言
TypeScript
星标
392
派生
22
平均合并
16 小时 56 分钟
30 天内合并 PR
298

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

githubnext/chopin 的其他 Issue

查看 githubnext/chopin 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。