hikoutei 0.10.9-dev → 0.10.11-dev

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.ja.md CHANGED
@@ -12,7 +12,7 @@ Google Sheets を利用する MVP 向けの型付きリポジトリであり、
12
12
  Sheets へ非同期で投影されます。
13
13
 
14
14
  <a href="https://www.npmjs.com/package/hikoutei">npm</a> ·
15
- <a href="docs/quick-start.md">クイックスタート</a> ·
15
+ <a href="website/guide/quick-start.md">クイックスタート</a> ·
16
16
  <a href="https://github.com/ManddarinShop/Hikoutei/issues">Issues</a>
17
17
 
18
18
  [![npm version](https://img.shields.io/npm/v/hikoutei?style=flat-square)](https://www.npmjs.com/package/hikoutei)
@@ -176,12 +176,12 @@ Hikoutei は、永続的なローカル outbox・冪等な配信・競合を考
176
176
  ため、一時的な API 障害でコミット済みのアプリケーション書き込みが失われる
177
177
  ことはありません。provider は資格情報・スプレッドシート ID・URL・ペイロードを
178
178
  ログに残さず、Google の割り当て枠に収まるようリクエスト開始間隔を調整します。
179
- 詳細な状態機械と復旧ルールは[内部整合性モデル](docs/internal-consistency-model.md)を
179
+ 詳細な状態機械と復旧ルールは[内部整合性モデル](website/guide/internal-consistency.md)を
180
180
  参照してください。
181
181
 
182
182
  ライブの Google 呼び出しはオプトインであり、通常の検証経路はフェイク
183
183
  provider と SQLite フィクスチャです。詳細なセットアップとトラブルシューティン
184
- グは[クイックスタート](docs/quick-start.md)を参照してください。
184
+ グは[クイックスタート](website/guide/quick-start.md)を参照してください。
185
185
 
186
186
  ## インストール
187
187
 
@@ -196,15 +196,15 @@ MikroORM は実装の詳細であり、Hikoutei の公開エンティティ API
196
196
 
197
197
  ## ドキュメント
198
198
 
199
- - [クイックスタート](docs/quick-start.md) — インストール、ORM ライフサイクル、
199
+ - [クイックスタート](website/guide/quick-start.md) — インストール、ORM ライフサイクル、
200
200
  サービス側の同期設定
201
- - [アーキテクチャ](docs/architecture.md) — ローカルストアとシートビューの関係
202
- - [書き込みと同期フロー](docs/write-and-synchronization-flow.md) — 非同期配信と
201
+ - [アーキテクチャ](website/guide/architecture.md) — ローカルストアとシートビューの関係
202
+ - [書き込みと同期フロー](website/guide/sync-flow.md) — 非同期配信と
203
203
  復旧動作
204
- - [内部整合性モデル](docs/internal-consistency-model.md) — 永続的な outbox、
204
+ - [内部整合性モデル](website/guide/internal-consistency.md) — 永続的な outbox、
205
205
  冪等な配信、競合を考慮した更新
206
- - [開発](docs/development.md) — ローカル開発とテストコマンド
207
- - [ベンチマークノート](docs/sync-bulk-write-benchmark.md) — 日付付きの測定と
206
+ - [開発](website/guide/contributing.md) — ローカル開発とテストコマンド
207
+ - [ベンチマークノート](website/guide/benchmarks.md) — 日付付きの測定と
208
208
  その限界
209
209
 
210
210
  ## 制限事項
package/README.ko.md CHANGED
@@ -11,7 +11,7 @@ Google Sheets 기반 MVP를 위한 타입 안전 리포지토리이자 안전한
11
11
  사람이 검토하고 가볍게 협업할 수 있도록 Google Sheets에 비동기로 투영됩니다.
12
12
 
13
13
  <a href="https://www.npmjs.com/package/hikoutei">npm</a> ·
14
- <a href="docs/quick-start.md">빠른 시작</a> ·
14
+ <a href="website/guide/quick-start.md">빠른 시작</a> ·
15
15
  <a href="https://github.com/ManddarinShop/Hikoutei/issues">이슈</a>
16
16
 
17
17
  [![npm version](https://img.shields.io/npm/v/hikoutei?style=flat-square)](https://www.npmjs.com/package/hikoutei)
@@ -169,11 +169,11 @@ Hikoutei는 내구성 있는 로컬 outbox, 멱등 전달, 충돌을 인지하
169
169
  사용하므로 일시적인 API 실패가 커밋된 애플리케이션 쓰기를 잃게 하지 않습니다.
170
170
  provider는 자격 증명, 스프레드시트 ID, URL, 페이로드를 로그에 남기지 않으며,
171
171
  Google 할당량 창 안에 머물도록 요청 시작 간격을 조절합니다. 상세 상태 머신과
172
- 복구 규칙은 [내부 정합성 모델](docs/internal-consistency-model.md)을
172
+ 복구 규칙은 [내부 정합성 모델](website/guide/internal-consistency.md)을
173
173
  참고하세요.
174
174
 
175
175
  라이브 Google 호출은 opt-in이며, 일반적인 검증 경로는 fake provider와 SQLite
176
- fixture입니다. 자세한 설정과 문제 해결 단계는 [빠른 시작](docs/quick-start.md)을
176
+ fixture입니다. 자세한 설정과 문제 해결 단계는 [빠른 시작](website/guide/quick-start.md)을
177
177
  참고하세요.
178
178
 
179
179
  ## 설치
@@ -190,14 +190,14 @@ MikroORM은 구현 세부 사항이며 Hikoutei의 공개 엔티티 API에는
190
190
 
191
191
  ## 문서
192
192
 
193
- - [빠른 시작](docs/quick-start.md) — 설치, ORM 생명주기, 서비스 측 동기화 설정
194
- - [아키텍처](docs/architecture.md) — 로컬 저장소와 Sheet 화면이 맞물리는 방식
195
- - [쓰기 및 동기화 흐름](docs/write-and-synchronization-flow.md) — 비동기 전달과
193
+ - [빠른 시작](website/guide/quick-start.md) — 설치, ORM 생명주기, 서비스 측 동기화 설정
194
+ - [아키텍처](website/guide/architecture.md) — 로컬 저장소와 Sheet 화면이 맞물리는 방식
195
+ - [쓰기 및 동기화 흐름](website/guide/sync-flow.md) — 비동기 전달과
196
196
  복구 동작
197
- - [내부 정합성 모델](docs/internal-consistency-model.md) — 내구성 outbox,
197
+ - [내부 정합성 모델](website/guide/internal-consistency.md) — 내구성 outbox,
198
198
  멱등 전달, 충돌을 인지하는 업데이트
199
- - [개발](docs/development.md) — 로컬 개발 및 테스트 명령어
200
- - [벤치마크 노트](docs/sync-bulk-write-benchmark.md) — 날짜가 기록된 측정과
199
+ - [개발](website/guide/contributing.md) — 로컬 개발 및 테스트 명령어
200
+ - [벤치마크 노트](website/guide/benchmarks.md) — 날짜가 기록된 측정과
201
201
  그 한계
202
202
 
203
203
  ## 한계
package/README.md CHANGED
@@ -123,11 +123,14 @@ client directly.
123
123
 
124
124
  Google Sheets synchronization is a service-side concern. Applications do not
125
125
  import a provider client, pass Sheet routes to `createTypedSheets()`, or choose
126
- an operation for each write — the root API accepts only `dbName` and
127
- `entities`. The sync runtime uses one internal Google Sheets API provider with
128
- a service account — no Apps Script deployment. Sync auto-start is selected by
129
- `HIKOUTEI_SYNC_SPREADSHEET_URL` plus `GOOGLE_APPLICATION_CREDENTIALS`; there is
130
- no public `googleSheetsApi` bootstrap option to configure.
126
+ an operation for each write — `CreateTypedSheetsOptions` fields (`dbName`,
127
+ `entities`, `providerOptions`) are all optional. The sync runtime uses one
128
+ internal Google Sheets API provider with a service account — no Apps Script
129
+ deployment. Sync auto-start is selected by `HIKOUTEI_SYNC_SPREADSHEET_URL`
130
+ plus `GOOGLE_APPLICATION_CREDENTIALS`. Optional `providerOptions` tunes the
131
+ sync-path provider (telemetry/timeouts; inert when local-only), and
132
+ `createTypedSheetsWithSync()` exposes the same options with a richer result
133
+ for existing-sheet adoption.
131
134
 
132
135
  **Fastest path:** install the gcloud CLI, then run `npx hikoutei setup` from your
133
136
  project directory. On an interactive terminal it offers (press Enter) to
@@ -247,8 +250,8 @@ shared on the spreadsheet (the error tells you which email to share).
247
250
  `GOOGLE_APPLICATION_CREDENTIALS` and `HIKOUTEI_SYNC_SPREADSHEET_URL` set;
248
251
  `createTypedSheets()` detects them and starts the internal sync bootstrap —
249
252
  it creates and verifies headers on the registered tabs, then starts outbox
250
- delivery and User_Input polling. There is no provider option to pass and no
251
- internal bootstrap to start by hand.
253
+ delivery and User_Input polling. Pass `providerOptions` only when sync-path
254
+ tuning is needed; there is no internal bootstrap to start by hand.
252
255
 
253
256
  > **Legacy spreadsheet note.** Spreadsheets provisioned by the old Apps Script
254
257
  > provider with developer-metadata row anchors are not migrated: `User_Input`
@@ -273,15 +276,15 @@ verification path. The detailed setup and troubleshooting steps are in the
273
276
 
274
277
  ## Installation
275
278
 
276
- The project and npm package are both called `hikoutei`. The built-in SQLite
277
- provider currently requires MikroORM:
279
+ The project and npm package are both called `hikoutei`. This repo uses pnpm
280
+ (packageManager `pnpm@11.1.2`):
278
281
 
279
282
  ```sh
280
- npm install hikoutei @mikro-orm/core @mikro-orm/sql
283
+ pnpm install --frozen-lockfile
281
284
  ```
282
285
 
283
- MikroORM is an implementation detail and does not appear in Hikoutei's public
284
- entity API.
286
+ `@mikro-orm/core` and `@mikro-orm/sql` are optional peers (`optional: true`),
287
+ lazy-loaded only when a runtime opens. `npm install` still works for consumers.
285
288
 
286
289
  ## Documentation
287
290
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hikoutei",
3
- "version": "0.10.9-dev",
3
+ "version": "0.10.11-dev",
4
4
  "description": "Typed repository and safe write layer for Google Sheets-backed MVPs. SQLite-authoritative entity lifecycle with asynchronous Google Sheets projection.",
5
5
  "repository": {
6
6
  "type": "git",