bunderstack-sync 0.12.0 → 0.16.0

package/README.md

@@ -23,6 +23,27 @@ ssr: {
 }
 ```
 
+Because `exports` point straight at source, your TypeScript and bundler
+resolve modules *inside this package's own directory* rather than a compiled
+`dist`. That makes a stray `node_modules/bunderstack-sync/node_modules/`
+uniquely dangerous: if one is ever present (e.g. left over from an earlier
+`link:`/`file:` dependency on a local checkout, then never cleaned up after
+switching to a registry version), both `tsc` and the bundler will resolve
+peer packages like `@tanstack/db`, `@tanstack/react-query`, or `react` from
+inside it instead of your app's own `node_modules`. Two copies of a
+context-carrying package means two separate module instances at runtime —
+collections, providers, or contexts from one copy become invisible to hooks
+from the other. If you hit unexplained "not found"/mismatched-type errors,
+check for nested `node_modules` under this package's install location before
+assuming it's an application bug:
+
+```sh
+find node_modules -path '*/bunderstack-sync/node_modules/@tanstack*'
+```
+
+A clean `rm -rf node_modules && bun install` removes any that a normal
+install wouldn't have produced on its own.
+
 ## License
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bunderstack-sync",
-  "version": "0.12.0",
+  "version": "0.16.0",
   "description": "TanStack DB collections synced live to a bunderstack backend: optimistic mutations with SSE-driven realtime sync.",
   "keywords": [
     "bun",
@@ -35,7 +35,7 @@
     "test": "bun test"
   },
   "dependencies": {
-    "bunderstack-query": "^0.12.0"
+    "bunderstack-query": "^0.16.0"
   },
   "devDependencies": {
     "@tanstack/db": "0.6.16",

package/src/collection.ts

@@ -1,10 +1,11 @@
+import type { QueryClient } from '@tanstack/react-query'
+
 import {
   createCollection,
   type Collection,
   type StandardSchema,
 } from '@tanstack/db'
 import { queryCollectionOptions } from '@tanstack/query-db-collection'
-import type { QueryClient } from '@tanstack/react-query'
 import {
   createTableClient,
   MAX_LIST_LIMIT,

package/src/index.ts

@@ -1,4 +1,5 @@
 import type { QueryClient } from '@tanstack/react-query'
+
 import {
   createBunderstackQueryClient,
   type FilesQueryClient,
@@ -8,9 +9,10 @@ import {
   type UploadedFile,
 } from 'bunderstack-query'
 
+import type { CreateFor, RowFor } from './sync-client'
+
 import { createTableCollection, type TableCollection } from './collection'
 import { createSyncRealtimeClient } from './realtime-sync'
-import type { CreateFor, RowFor } from './sync-client'
 
 type BaseOptions = {
   baseUrl?: string
@@ -70,32 +72,28 @@ export function createBunderstackSyncClient<
         })
 
       // Realtime needs a browser-side persistent connection; default off in SSR.
-      const realtime =
-        !(options.realtime ?? typeof window !== 'undefined')
-          ? undefined
-          : createSyncRealtimeClient({
-              baseUrl,
-              queryClient: options.queryClient,
-              // `createSyncRealtimeClient` expects the ambient `typeof fetch`
-              // (which includes Bun's `preconnect` static), while our public
-              // options accept any plain fetch-shaped function — the two
-              // signatures are otherwise call-compatible.
-              fetch: fetchFn as typeof fetch,
-              // Individual collections are typed against their own row shape
-              // (inferred from `createTableCollection`'s constraint since
-              // this loop can't carry a per-key TRow), which is narrower
-              // than `SyncableCollection`'s `unknown`-typed utils. Safe here
-              // because `realtime-sync.ts` only ever passes server-decoded
-              // records through, matching each collection's own row shape.
-              collections: Object.fromEntries(
-                Object.entries(tablesClient).map(([k, v]) => [
-                  k,
-                  v.collection,
-                ]),
-              ) as unknown as NonNullable<
-                Parameters<typeof createSyncRealtimeClient>[0]['collections']
-              >,
-            })
+      const realtime = !(options.realtime ?? typeof window !== 'undefined')
+        ? undefined
+        : createSyncRealtimeClient({
+            baseUrl,
+            queryClient: options.queryClient,
+            // `createSyncRealtimeClient` expects the ambient `typeof fetch`
+            // (which includes Bun's `preconnect` static), while our public
+            // options accept any plain fetch-shaped function — the two
+            // signatures are otherwise call-compatible.
+            fetch: fetchFn as typeof fetch,
+            // Individual collections are typed against their own row shape
+            // (inferred from `createTableCollection`'s constraint since
+            // this loop can't carry a per-key TRow), which is narrower
+            // than `SyncableCollection`'s `unknown`-typed utils. Safe here
+            // because `realtime-sync.ts` only ever passes server-decoded
+            // records through, matching each collection's own row shape.
+            collections: Object.fromEntries(
+              Object.entries(tablesClient).map(([k, v]) => [k, v.collection]),
+            ) as unknown as NonNullable<
+              Parameters<typeof createSyncRealtimeClient>[0]['collections']
+            >,
+          })
 
       return {
         ...tablesClient,

package/src/realtime-sync.ts

@@ -1,6 +1,7 @@
-import { createRealtimeClient, type RealtimeEvent } from 'bunderstack-query'
 import type { QueryClient } from '@tanstack/react-query'
 
+import { createRealtimeClient, type RealtimeEvent } from 'bunderstack-query'
+
 type SyncableCollection = {
   utils: {
     writeUpsert: (item: unknown) => void

package/src/sync-client.ts

@@ -1,4 +1,5 @@
 import type { QueryClient } from '@tanstack/react-query'
+
 import {
   attachBucketMutationOptions,
   createBucketClient,
@@ -24,8 +25,8 @@ export type RowFor<
 > = [InferSelect<TSchema[K]>] extends [never]
   ? { id: string | number }
   : InferSelect<TSchema[K]> extends { id: string | number }
-  ? InferSelect<TSchema[K]>
-  : { id: string | number }
+    ? InferSelect<TSchema[K]>
+    : { id: string | number }
 
 export type CreateFor<
   TSchema extends Record<string, unknown>,