@vtex/faststore 0.0.2 → 0.0.4

package/CHANGELOG.md

@@ -4,6 +4,51 @@ Every published version of `@vtex/faststore` has a section here. From `0.0.2` on
 written when its release pull request opens, and reviewed alongside the API delta that justifies the
 version.
 
+## 0.0.4
+
+`./components` adds `MyAccountProfile`, the signed-in shopper's profile editor. `Root` loads the saved
+profile, renders its `Skeleton` until the data resolves, and renders nothing for an anonymous
+shopper. Save validates every field, sends only the changed ones in one
+`$actions.identity.customerProfileUpdate`, and focuses the first invalid field; Cancel restores the
+saved values. The frame parts are `EditButton`, `SaveButton`, `CancelButton` and `Email`, and the
+field controls are `FirstNameControl`, `LastNameControl`, `PhoneControl`, `BirthDateControl`,
+`GenderControl` and `TaxIdControl`. Each part has its own `*Definition` and `*Props` export, and
+`useMyAccountProfile`, `MyAccountProfileContextValue` and `MyAccountProfileData` come with them.
+Nothing is removed from `./components`.
+
+The peer dependencies are no longer optional: `@apollo/client`, `@apollo/client-integration-nextjs`,
+`next`, `react` and `react-dom` are required. `./client`, `./components` and `./internal/server`
+import them directly, and a store outside this repository that never declared `@apollo/client` itself
+failed with `Can't resolve '@apollo/client/react'` because package managers skip optional peers.
+npm 7+ and pnpm 8+ now install them for you. `.`, `./client` and `./graphql` have no signature change,
+so for them this is the only difference.
+
+## 0.0.3
+
+`./components` adds `SignInRedirect`, the component a store's `/login` page renders to hand the
+shopper over to the platform login. It comes with `SignInRedirectLoading`, the
+`SignInRedirectContent` content type for the waiting message, `SignInRedirectDefinition`, and the
+`SignInRedirectProps` and `SignInRedirectLoadingProps` types.
+
+Five `./components` signatures now take their props as `Readonly<...>`: `ClientProfileFormRoot`,
+`ClientProfilePhoneControl`, `DeliveryOptionsController`, `IdentitySummaryRoot` and
+`ShippingAddressRoot`. Nothing changes for code that renders them.
+
+Action providers now deliver `$actions` through context instead of `cloneElement`, so a child that
+crosses the React Server Components boundary as a lazy reference receives its actions. The
+signatures are unchanged.
+
+The GraphQL client that `./internal/server` builds forwards the shopper's `Cookie` header into
+server-rendered queries, so a signed-in shopper's server render is no longer anonymous. A
+caller-supplied `Cookie` header wins, and outside a Next.js request the client sends none.
+
+`dist/catalog.json` is now built by `@vtex/faststore-catalog`, and its `docPath` values are relative
+to the package (`src/...`). `.`, `./client` and `./graphql` are unchanged.
+
+This is the first version released in two sets at once (ADR-0004). The Public set goes to npmjs,
+including the first real `@vtex/faststore-catalog` version, and the Internal set goes to
+CodeArtifact, including the first `@vtex/sukima` that carries the command and the library together.
+
 ## 0.0.2
 
 No change to the public API surface across the four snapshotted entries (`.`, `./client`,

package/README.md

@@ -14,8 +14,10 @@ The version line is `0.0.x`. Under semver every patch may break, and a caret ran
 Nothing here is a compatibility promise yet: 138 types are reachable through the public entries without being
 named in them, and the authoring loop this SDK belongs to is not finished.
 
-This release makes the SDK installable and importable. It does not yet make an extension package buildable
-outside the FastStore repository — the catalog build runs through the `faststore` CLI, which is not published.
+This release makes the SDK installable and importable, and it publishes the catalog build alongside it as
+`@vtex/faststore-catalog`. It does not yet make an extension package buildable outside the FastStore
+repository: what is still missing is the `faststore` CLI that wires that build into an extension's `build`
+script, and it is not published.
 
 ## Entry points
 
@@ -64,7 +66,7 @@ These carry no snapshot. Treat their shape as unstable while the package is pre-
 
 ## Peer dependencies
 
-All five are optional:
+All five are required:
 
 | Peer | Range |
 | --- | --- |
@@ -77,8 +79,12 @@ All five are optional:
 They are peers rather than dependencies so the app resolves one copy of each. Two copies of `@apollo/client`
 mean two caches, and the reactive state behind the hooks would split across them.
 
-They are optional because the entries are audience-split: an API Extension that only imports `./graphql` needs
-none of them. Install whatever your entries require.
+None is marked optional. `./client`, `./components`, and `./internal/server` import `@apollo/client`,
+`@apollo/client-integration-nextjs`, and `next` directly, so a store using any of those entries cannot run
+without them. Package managers that auto-install peers (npm 7+, pnpm 8+) install them for you.
+
+An API Extension that imports only `./graphql` never uses any of them; installing them anyway costs disk,
+not correctness.
 
 ## Styling