V5 : Split package, formatter support and Jotai 2.20 support

.changeset/many-poems-count.md

@@ -0,0 +1,5 @@
+---
+'jotai-logger': minor
+---
+
+fix: retroactively set dependents and pendingPromises on initialized/mounted events

.changeset/neat-pens-appear.md

@@ -0,0 +1,19 @@
+---
+'jotai-logger': major
+---
+
+Split the package into vanilla/react/formatter entry points
+
+- Split the core logger from its console formatter.
+- The core handle only scheduling and filtering options and accepts a new `formatter` option.
+- The new `consoleFormatter` factory creates the built in console formatter and accepts the old display options (`domain`, `logger`, `colorScheme`, etc.).
+- Add the `formatter` option to `bindAtomsLoggerToStore` and `useAtomsLogger` to replace the default console output with any custom function.
+
+BREAKING CHANGE:
+
+Formatting options that were present in `bindAtomsLoggerToStore` and `useAtomsLogger` are now moved to the new `consoleFormatter` factory options.
+
+```diff
+- bindAtomsLoggerToStore(store, { stringifyLimit: 100 });
++ const loggedStore = createLoggedStore(store, { formatter: consoleFormatter({ stringifyLimit: 100 }) });
+```

.changeset/olive-toes-lay.md

@@ -0,0 +1,5 @@
+---
+'jotai-logger': patch
+---
+
+fix: track dependencies that have the same name

.changeset/pretty-signs-stick.md

@@ -0,0 +1,5 @@
+---
+'jotai-logger': patch
+---
+
+fix: don't add empty or undefined data to events

.changeset/real-cars-nail.md

@@ -0,0 +1,12 @@
+---
+'jotai-logger': major
+---
+
+Jotai 2.20 support
+
+Adds support for Jotai 2.20's new internal `INTERNAL_buildStoreRev3` API
+(see [pmndrs/jotai#3293](https://github.com/pmndrs/jotai/pull/3293)).
+
+BREAKING CHANGE:
+
+Only jotai 2.20.0 and up is supported due to changes in their internal APIs.

.changeset/sixty-sheep-fetch.md

@@ -0,0 +1,18 @@
+---
+'jotai-logger': major
+---
+
+Replace the mutation-based API with a derived-store API
+
+- The store is no longer mutated. Instead, `createLoggedStore` returns a **new** store that shares all internal state with the parent but intercepts `get`, `set` and `sub` for logging.
+- On the React side, `AtomLoggerProvider` propagates the logged store to children via a Jotai `<Provider>`, retrieving the parent store from context automatically.
+- This approach aligns with Jotai's internal `INTERNAL_buildStoreRev2` API introduced in jotai v2.15 (see https://github.com/pmndrs/jotai/pull/3149).
+
+BREAKING CHANGE:
+
+A migration guide from v4 to v5 is present in the README. [See link](https://github.com/Wendystraite/jotai-logger#migration-guide). TLDR:
+
+- `useAtomsLogger` is replaced by `AtomLoggerProvider`, a Provider-like component that automatically picks up the nearest Jotai store from context and wraps children in a new logged store.
+- `bindAtomsLoggerToStore` is replaced by `createLoggedStore` that creates and return a new store.
+- `isAtomsLoggerBoundToStore` removed → use `isLoggedStore`
+- `createLoggedStore` **throws** instead of returning `false`

.github/workflows/ci.yml

@@ -38,3 +38,5 @@ jobs:
         uses: codecov/codecov-action@v5
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
+
+      - run: pnpm exec pkg-pr-new publish --commentWithSha