@ledgerhq/live-env 4.0.1-nightly.20260924020607 → 4.1.0

package/CHANGELOG.md

@@ -1,345 +1,11 @@
 # @ledgerhq/live-env
 
-## 4.0.1-nightly.20260924020607
-
-### Patch Changes
-
-- [#22006](https://github.com/LedgerHQ/ledger-live/pull/22006) [`a62ad28`](https://github.com/LedgerHQ/ledger-live/commit/a62ad28e4900a887567fb61fb8f197af4fa5a23b) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Point the deprecation notices at `docs/configuration.md`, which is now the single guide for where a configuration value belongs and how to take one out of the env registry. `libs/env/MIGRATION.md` and `shared/env/MIGRATION.md` are removed — their content lives there, next to the app `.env` and build-secret mechanics it was already linking to. Comments and docs only.
-
-## 4.0.0
-
-### Major Changes
-
-- [#21409](https://github.com/LedgerHQ/ledger-live/pull/21409) [`b9e15ac`](https://github.com/LedgerHQ/ledger-live/commit/b9e15ac78e2b89919c605511f333282610e57225) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Remove the `EnvTypes` registry
-
-  `injectDefinitions()` already moved every env-var default out of the framework, but `EnvTypes` stayed behind and kept the full list of env names and their types inside the library. It is gone, along with the `EnvName` / `EnvValue` exports and the typed `getEnv` / `setEnv` / `getEnvDefault` overloads built on it.
-
-  `getEnv(name)` and `getEnvDefault(name)` now return `any`, so existing call sites keep compiling. A consumer that wants typing declares the vars it reads and wraps the accessor:
-
-  ```ts
-  import { getEnv as getEnvUnsafe } from "@ledgerhq/live-env";
-
-  type Envs = { MY_TIMEOUT: number; MY_API_URL: string };
-
-  export const getEnv = <K extends keyof Envs>(name: K): Envs[K] =>
-    getEnvUnsafe(name);
-  ```
-
-### Minor Changes
-
-- [#21544](https://github.com/LedgerHQ/ledger-live/pull/21544) [`b7a8906`](https://github.com/LedgerHQ/ledger-live/commit/b7a89064587bbcd1f758f7b6205a616225ac2317) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Mark the whole public API deprecated and ship the migration guide. `getEnv`, `setEnv`, `setEnvUnsafe`, `getEnvDefault`, `getAllEnvs`, `injectDefinitions`, `changes`, the registry introspection helpers, the exported types and the `useEnv` hook now carry `@deprecated`. `libs/env/MIGRATION.md` documents the four exits every variable takes; `shared/env/MIGRATION.md` covers what that means inside ledger-live. No behaviour change.
-
-## 4.0.0-next.0
-
-### Major Changes
-
-- [#21409](https://github.com/LedgerHQ/ledger-live/pull/21409) [`b9e15ac`](https://github.com/LedgerHQ/ledger-live/commit/b9e15ac78e2b89919c605511f333282610e57225) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Remove the `EnvTypes` registry
-
-  `injectDefinitions()` already moved every env-var default out of the framework, but `EnvTypes` stayed behind and kept the full list of env names and their types inside the library. It is gone, along with the `EnvName` / `EnvValue` exports and the typed `getEnv` / `setEnv` / `getEnvDefault` overloads built on it.
-
-  `getEnv(name)` and `getEnvDefault(name)` now return `any`, so existing call sites keep compiling. A consumer that wants typing declares the vars it reads and wraps the accessor:
-
-  ```ts
-  import { getEnv as getEnvUnsafe } from "@ledgerhq/live-env";
-
-  type Envs = { MY_TIMEOUT: number; MY_API_URL: string };
-
-  export const getEnv = <K extends keyof Envs>(name: K): Envs[K] =>
-    getEnvUnsafe(name);
-  ```
-
-### Minor Changes
-
-- [#21544](https://github.com/LedgerHQ/ledger-live/pull/21544) [`b7a8906`](https://github.com/LedgerHQ/ledger-live/commit/b7a89064587bbcd1f758f7b6205a616225ac2317) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Mark the whole public API deprecated and ship the migration guide. `getEnv`, `setEnv`, `setEnvUnsafe`, `getEnvDefault`, `getAllEnvs`, `injectDefinitions`, `changes`, the registry introspection helpers, the exported types and the `useEnv` hook now carry `@deprecated`. `libs/env/MIGRATION.md` documents the four exits every variable takes; `shared/env/MIGRATION.md` covers what that means inside ledger-live. No behaviour change.
-
-## 3.2.0
-
-### Minor Changes
-
-- [#21124](https://github.com/LedgerHQ/ledger-live/pull/21124) [`e21305a`](https://github.com/LedgerHQ/ledger-live/commit/e21305abce18f0a9408bf6c0e2bb47d5c992e06a) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Make getEnv and getEnvDefault throw when the name is not in injected definitions
-
-## 3.2.0-next.0
-
-### Minor Changes
-
-- [#21124](https://github.com/LedgerHQ/ledger-live/pull/21124) [`e21305a`](https://github.com/LedgerHQ/ledger-live/commit/e21305abce18f0a9408bf6c0e2bb47d5c992e06a) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Make getEnv and getEnvDefault throw when the name is not in injected definitions
-
-## 3.1.0
-
-### Minor Changes
-
-- [#20998](https://github.com/LedgerHQ/ledger-live/pull/20998) [`8161bac`](https://github.com/LedgerHQ/ledger-live/commit/8161bac542474212dfefc8519e714da345b03f71) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - chore: move hedera envs directly to config
-
-- [#20650](https://github.com/LedgerHQ/ledger-live/pull/20650) [`fbc8036`](https://github.com/LedgerHQ/ledger-live/commit/fbc8036d9bd4e1cc30eea4233f05e8b0498c0e5e) Thanks [@lysyi3m](https://github.com/lysyi3m)! - Add a gRPC-web transport to the Sui coin module
-
-  - `coin-sui` gains a third transport on `sui.rpc.v2` over gRPC-web, covering every capability from
-    checkpoints to device signing.
-  - New tri-state `suiTransport` feature flag (`json` | `grpc` | `graphql`), defaulting to `json`,
-    replaces the boolean `suiGraphqlTransport`, which is removed. An unrecognised value resolves to
-    `json`.
-  - New env vars `API_SUI_GRPC_PROXY` and `API_SUI_TESTNET_GRPC_PROXY`. `@mysten/sui` 2.9.0 → 2.23.1.
-  - Operation `blockHash` carries the real checkpoint digest on gRPC.
-  - Fix: account sync read a single page of history on GraphQL and gRPC, capping an account at its
-    newest 50 operations for good — sync resumes from the newest stored operation and never re-reads
-    what it skipped. Both arms now walk up to `TRANSACTIONS_LIMIT` (300), the depth JSON-RPC reached.
-  - Fix: a resumed sync on GraphQL and gRPC read backwards from the tip, so when more than
-    `TRANSACTIONS_LIMIT` transactions arrived between two syncs, the ones in the middle were skipped
-    and the next sync resumed above them — a permanent hole. Both arms now walk forward from the
-    cursor, as the JSON-RPC arm already did, leaving anything unread newer than the next resume point.
-  - Fix: an account holding no operations resumed from its stored `syncHash`, so a cleared cache came
-    back with only the transactions that arrived after it. Such an account now re-reads its history,
-    which is also how one truncated by the bug above recovers. Token operations count as history: they
-    live in the subaccounts, so a token-only account is no longer treated as empty.
-  - Fix: on gRPC, any failure to resolve a cursor's digest — including a transient network error — was
-    read as "unknown digest", which falls back to an unbounded page from the tip and made paging report
-    the end of history. Only a `NOT_FOUND` does that now; everything else propagates and is retried.
-  - Fix: reading history skipped transactions that shared a checkpoint with the resume point, in
-    account sync (`getOperations`) as well as paging (`getListOperations`).
-  - Fix: paging inferred "more to come" from how many operations survived client-side filtering, which
-    ended the walk early. GraphQL now reads `pageInfo`, gRPC the stream's `QueryEnd` reason. A page
-    whose transactions were all filtered out now resumes from the page's own boundary instead of
-    reporting the end of history.
-  - Fix: a gRPC history record with no timestamp became an operation dated 1970 that could not serve as
-    a pagination cursor. Those records are now dropped, as the GraphQL arm already did.
-  - Fix: ascending paging on GraphQL returned the newest slice of the range instead of walking forward
-    from the oldest.
-  - Fix: the Sui fetcher dropped `X-Ledger-Client-Version` and all gRPC-web headers when passed a
-    `Headers` instance.
-  - Fix: GraphQL resolved the latest checkpoint in two queries, so the second could answer null. It is
-    now one query.
-  - A checkpoint missing its `digest` or `timestamp` now raises on both GraphQL and gRPC, instead of
-    reporting a block with an empty hash and a 1970 timestamp.
-  - Known limitation: `getListOperations` resumes from a synthesised `timestamp:digest` cursor, so
-    within one checkpoint a sibling whose digest sorts earlier can be skipped, and a checkpoint holding
-    more than one page is stepped over rather than resumed inside. Account sync is unaffected: it
-    resumes from the server's own watermark cursor.
-
-- [#20955](https://github.com/LedgerHQ/ledger-live/pull/20955) [`39a676d`](https://github.com/LedgerHQ/ledger-live/commit/39a676d2f861d04913264e61100205b4f6044cf9) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - fix: move hedera envs to config/constants
-
-## 3.1.0-next.0
-
-### Minor Changes
-
-- [#20998](https://github.com/LedgerHQ/ledger-live/pull/20998) [`8161bac`](https://github.com/LedgerHQ/ledger-live/commit/8161bac542474212dfefc8519e714da345b03f71) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - chore: move hedera envs directly to config
-
-- [#20650](https://github.com/LedgerHQ/ledger-live/pull/20650) [`fbc8036`](https://github.com/LedgerHQ/ledger-live/commit/fbc8036d9bd4e1cc30eea4233f05e8b0498c0e5e) Thanks [@lysyi3m](https://github.com/lysyi3m)! - Add a gRPC-web transport to the Sui coin module
-
-  - `coin-sui` gains a third transport on `sui.rpc.v2` over gRPC-web, covering every capability from
-    checkpoints to device signing.
-  - New tri-state `suiTransport` feature flag (`json` | `grpc` | `graphql`), defaulting to `json`,
-    replaces the boolean `suiGraphqlTransport`, which is removed. An unrecognised value resolves to
-    `json`.
-  - New env vars `API_SUI_GRPC_PROXY` and `API_SUI_TESTNET_GRPC_PROXY`. `@mysten/sui` 2.9.0 → 2.23.1.
-  - Operation `blockHash` carries the real checkpoint digest on gRPC.
-  - Fix: account sync read a single page of history on GraphQL and gRPC, capping an account at its
-    newest 50 operations for good — sync resumes from the newest stored operation and never re-reads
-    what it skipped. Both arms now walk up to `TRANSACTIONS_LIMIT` (300), the depth JSON-RPC reached.
-  - Fix: a resumed sync on GraphQL and gRPC read backwards from the tip, so when more than
-    `TRANSACTIONS_LIMIT` transactions arrived between two syncs, the ones in the middle were skipped
-    and the next sync resumed above them — a permanent hole. Both arms now walk forward from the
-    cursor, as the JSON-RPC arm already did, leaving anything unread newer than the next resume point.
-  - Fix: an account holding no operations resumed from its stored `syncHash`, so a cleared cache came
-    back with only the transactions that arrived after it. Such an account now re-reads its history,
-    which is also how one truncated by the bug above recovers. Token operations count as history: they
-    live in the subaccounts, so a token-only account is no longer treated as empty.
-  - Fix: on gRPC, any failure to resolve a cursor's digest — including a transient network error — was
-    read as "unknown digest", which falls back to an unbounded page from the tip and made paging report
-    the end of history. Only a `NOT_FOUND` does that now; everything else propagates and is retried.
-  - Fix: reading history skipped transactions that shared a checkpoint with the resume point, in
-    account sync (`getOperations`) as well as paging (`getListOperations`).
-  - Fix: paging inferred "more to come" from how many operations survived client-side filtering, which
-    ended the walk early. GraphQL now reads `pageInfo`, gRPC the stream's `QueryEnd` reason. A page
-    whose transactions were all filtered out now resumes from the page's own boundary instead of
-    reporting the end of history.
-  - Fix: a gRPC history record with no timestamp became an operation dated 1970 that could not serve as
-    a pagination cursor. Those records are now dropped, as the GraphQL arm already did.
-  - Fix: ascending paging on GraphQL returned the newest slice of the range instead of walking forward
-    from the oldest.
-  - Fix: the Sui fetcher dropped `X-Ledger-Client-Version` and all gRPC-web headers when passed a
-    `Headers` instance.
-  - Fix: GraphQL resolved the latest checkpoint in two queries, so the second could answer null. It is
-    now one query.
-  - A checkpoint missing its `digest` or `timestamp` now raises on both GraphQL and gRPC, instead of
-    reporting a block with an empty hash and a 1970 timestamp.
-  - Known limitation: `getListOperations` resumes from a synthesised `timestamp:digest` cursor, so
-    within one checkpoint a sibling whose digest sorts earlier can be skipped, and a checkpoint holding
-    more than one page is stepped over rather than resumed inside. Account sync is unaffected: it
-    resumes from the server's own watermark cursor.
-
-- [#20955](https://github.com/LedgerHQ/ledger-live/pull/20955) [`39a676d`](https://github.com/LedgerHQ/ledger-live/commit/39a676d2f861d04913264e61100205b4f6044cf9) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - fix: move hedera envs to config/constants
-
-## 3.0.0
-
-### Major Changes
-
-- [#20076](https://github.com/LedgerHQ/ledger-live/pull/20076) [`c475d28`](https://github.com/LedgerHQ/ledger-live/commit/c475d288b4978aa3011c9e76f3e9a1e2f9733010) Thanks [@gre-ledger](https://github.com/gre-ledger)! - **Breaking change**: all env API functions (`getEnv`, `setEnv`, `setEnvUnsafe`, `getEnvDefault`, `getAllEnvs`, `getAllEnvNames`, `getDefinition`, `getEnvDesc`, `isEnvDefault`) now throw if called before `injectDefinitions()`.
-
-  Previously, `@ledgerhq/live-env` bundled ~200 env var definitions and made them available on import. The definitions have been extracted into the new workspace-private `@shared/env` package. The framework layer (`@ledgerhq/live-env`) is now definition-free and requires an explicit bootstrap call.
-
-  **Migration for app consumers** — switch to `@shared/env` (recommended):
-
-  ```ts
-  // before
-  import { getEnv } from "@ledgerhq/live-env";
-
-  // after
-  import { getEnv } from "@shared/env"; // auto-calls injectDefinitions at import time
-  ```
-
-  **Migration for published libs** that need `@ledgerhq/live-env` directly (e.g. test setup):
-
-  ```ts
-  import { injectDefinitions, stringParser } from "@ledgerhq/live-env";
-
-  injectDefinitions({
-    MY_VAR: { def: "default", parser: stringParser, desc: "..." },
-  });
-  // now getEnv / setEnv work
-  ```
-
-  New exports: `injectDefinitions`, `EnvDef<T>`, `EnvDefs`, `EnvChange`, and all parser helpers (`intParser`, `floatParser`, `boolParser`, `stringParser`, `jsonParser`, `stringArrayParser`).
-
-## 3.0.0-next.0
-
-### Major Changes
-
-- [#20076](https://github.com/LedgerHQ/ledger-live/pull/20076) [`c475d28`](https://github.com/LedgerHQ/ledger-live/commit/c475d288b4978aa3011c9e76f3e9a1e2f9733010) Thanks [@gre-ledger](https://github.com/gre-ledger)! - **Breaking change**: all env API functions (`getEnv`, `setEnv`, `setEnvUnsafe`, `getEnvDefault`, `getAllEnvs`, `getAllEnvNames`, `getDefinition`, `getEnvDesc`, `isEnvDefault`) now throw if called before `injectDefinitions()`.
-
-  Previously, `@ledgerhq/live-env` bundled ~200 env var definitions and made them available on import. The definitions have been extracted into the new workspace-private `@shared/env` package. The framework layer (`@ledgerhq/live-env`) is now definition-free and requires an explicit bootstrap call.
-
-  **Migration for app consumers** — switch to `@shared/env` (recommended):
-
-  ```ts
-  // before
-  import { getEnv } from "@ledgerhq/live-env";
-
-  // after
-  import { getEnv } from "@shared/env"; // auto-calls injectDefinitions at import time
-  ```
-
-  **Migration for published libs** that need `@ledgerhq/live-env` directly (e.g. test setup):
-
-  ```ts
-  import { injectDefinitions, stringParser } from "@ledgerhq/live-env";
-
-  injectDefinitions({
-    MY_VAR: { def: "default", parser: stringParser, desc: "..." },
-  });
-  // now getEnv / setEnv work
-  ```
-
-  New exports: `injectDefinitions`, `EnvDef<T>`, `EnvDefs`, `EnvChange`, and all parser helpers (`intParser`, `floatParser`, `boolParser`, `stringParser`, `jsonParser`, `stringArrayParser`).
-
-## 2.42.0
-
-### Minor Changes
-
-- [#19439](https://github.com/LedgerHQ/ledger-live/pull/19439) [`a15b864`](https://github.com/LedgerHQ/ledger-live/commit/a15b864576d901f15d480070b475314c3b23c1dd) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Update default values for `CAL_SERVICE_URL` and `CAL_SERVICE_URL_STAGING` to the Gravitee gateway URLs (`https://global.api.prd.ledger.com/cal` and `https://global.api.stg.ledger-test.com/cal`).
-
-- [#19507](https://github.com/LedgerHQ/ledger-live/pull/19507) [`fc44f1e`](https://github.com/LedgerHQ/ledger-live/commit/fc44f1e6ddcca939c117e0cb8bc49c404163b003) Thanks [@Moustafa-Koterba](https://github.com/Moustafa-Koterba)! - feat(solana): update default validators summary base url for prod
-
-## 2.42.0-next.0
-
-### Minor Changes
-
-- [#19439](https://github.com/LedgerHQ/ledger-live/pull/19439) [`a15b864`](https://github.com/LedgerHQ/ledger-live/commit/a15b864576d901f15d480070b475314c3b23c1dd) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Update default values for `CAL_SERVICE_URL` and `CAL_SERVICE_URL_STAGING` to the Gravitee gateway URLs (`https://global.api.prd.ledger.com/cal` and `https://global.api.stg.ledger-test.com/cal`).
-
-- [#19507](https://github.com/LedgerHQ/ledger-live/pull/19507) [`fc44f1e`](https://github.com/LedgerHQ/ledger-live/commit/fc44f1e6ddcca939c117e0cb8bc49c404163b003) Thanks [@Moustafa-Koterba](https://github.com/Moustafa-Koterba)! - feat(solana): update default validators summary base url for prod
-
-## 2.41.0
-
-### Minor Changes
-
-- [#19231](https://github.com/LedgerHQ/ledger-live/pull/19231) [`70a706e`](https://github.com/LedgerHQ/ledger-live/commit/70a706e4efe3a6fa176f9827a4a06949ba185f11) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Remove unused USE_LEARN_STAGING_URL env var
-
-## 2.41.0-next.0
-
-### Minor Changes
-
-- [#19231](https://github.com/LedgerHQ/ledger-live/pull/19231) [`70a706e`](https://github.com/LedgerHQ/ledger-live/commit/70a706e4efe3a6fa176f9827a4a06949ba185f11) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Remove unused USE_LEARN_STAGING_URL env var
-
-## 2.40.0
-
-### Minor Changes
-
-- [#18823](https://github.com/LedgerHQ/ledger-live/pull/18823) [`13aeeb6`](https://github.com/LedgerHQ/ledger-live/commit/13aeeb6186997b433785e542ed1dafa6afde2267) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - chore: remove unused thirdweb code
-
-- [#17970](https://github.com/LedgerHQ/ledger-live/pull/17970) [`798081d`](https://github.com/LedgerHQ/ledger-live/commit/798081db3e427c8d2d09930ceb836703146ca1ba) Thanks [@YazhuEth](https://github.com/YazhuEth)! - Migrate the Polkadot family (mainnet and Westend, relay chain and asset hub) to the new polkadot-rest-api endpoints, served under a `/v1` prefix (`/v1/rc` for the relay chain).
-
-  Adapt the coin-polkadot client to the rest-api, which is not fully 1:1 with substrate-api-sidecar:
-
-  - staking storage queries use `keys[]` only (drop the legacy `key1` query param, rejected by the rest-api);
-  - tolerate a missing `ss58Format` in `/runtime/spec` (e.g. Westend Asset Hub) instead of producing `NaN`;
-  - parse the new `/transaction/dry-run` response shape (`resultType` at the root, error under `result.error`, plus the `TransactionValidityError` case).
-
-## 2.40.0-next.0
-
-### Minor Changes
-
-- [#18823](https://github.com/LedgerHQ/ledger-live/pull/18823) [`13aeeb6`](https://github.com/LedgerHQ/ledger-live/commit/13aeeb6186997b433785e542ed1dafa6afde2267) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - chore: remove unused thirdweb code
-
-- [#17970](https://github.com/LedgerHQ/ledger-live/pull/17970) [`798081d`](https://github.com/LedgerHQ/ledger-live/commit/798081db3e427c8d2d09930ceb836703146ca1ba) Thanks [@YazhuEth](https://github.com/YazhuEth)! - Migrate the Polkadot family (mainnet and Westend, relay chain and asset hub) to the new polkadot-rest-api endpoints, served under a `/v1` prefix (`/v1/rc` for the relay chain).
-
-  Adapt the coin-polkadot client to the rest-api, which is not fully 1:1 with substrate-api-sidecar:
-
-  - staking storage queries use `keys[]` only (drop the legacy `key1` query param, rejected by the rest-api);
-  - tolerate a missing `ss58Format` in `/runtime/spec` (e.g. Westend Asset Hub) instead of producing `NaN`;
-  - parse the new `/transaction/dry-run` response shape (`resultType` at the root, error under `result.error`, plus the `TransactionValidityError` case).
-
-## 2.39.0
-
-### Minor Changes
-
-- [#18395](https://github.com/LedgerHQ/ledger-live/pull/18395) [`81ceb34`](https://github.com/LedgerHQ/ledger-live/commit/81ceb347c0b2167358c601a9922e2c7fa14a845b) Thanks [@pawell24](https://github.com/pawell24)! - fix: point aptos testnet endpoints to public aptos backend
-
-- [#18320](https://github.com/LedgerHQ/ledger-live/pull/18320) [`9ab3a61`](https://github.com/LedgerHQ/ledger-live/commit/9ab3a6157abb3a382c3157eb292ce9d9d2c6df93) Thanks [@ishaba](https://github.com/ishaba)! - fix: sui testnet node url update
-
-- [#18256](https://github.com/LedgerHQ/ledger-live/pull/18256) [`eb1dae8`](https://github.com/LedgerHQ/ledger-live/commit/eb1dae8fc14ff8e0bc1e1ce040712492a0328451) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Derive "supported currencies" from the coin-modules registry instead of `setSupportedCurrencies`.
-
-  Each `CoinModuleLoader` now declares a `supportedCoins: CryptoCurrencyId[]` field, and a currency is supported when it appears in a registered loader's `supportedCoins`. The framework `setSupportedCurrencies` / `listSupportedCurrencies` / `isCurrencySupported` and the `EXPERIMENTAL_CURRENCIES` env are removed; `listSupportedCurrencies` / `isCurrencySupported` are now exported from `@ledgerhq/live-common/currencies` backed by the registry. Apps no longer maintain a supported-currencies list — registering the coin modules is what makes their currencies supported.
-
-## 2.39.0-next.0
+## 4.1.0
 
 ### Minor Changes
 
-- [#18395](https://github.com/LedgerHQ/ledger-live/pull/18395) [`81ceb34`](https://github.com/LedgerHQ/ledger-live/commit/81ceb347c0b2167358c601a9922e2c7fa14a845b) Thanks [@pawell24](https://github.com/pawell24)! - fix: point aptos testnet endpoints to public aptos backend
-
-- [#18320](https://github.com/LedgerHQ/ledger-live/pull/18320) [`9ab3a61`](https://github.com/LedgerHQ/ledger-live/commit/9ab3a6157abb3a382c3157eb292ce9d9d2c6df93) Thanks [@ishaba](https://github.com/ishaba)! - fix: sui testnet node url update
-
-- [#18256](https://github.com/LedgerHQ/ledger-live/pull/18256) [`eb1dae8`](https://github.com/LedgerHQ/ledger-live/commit/eb1dae8fc14ff8e0bc1e1ce040712492a0328451) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Derive "supported currencies" from the coin-modules registry instead of `setSupportedCurrencies`.
-
-  Each `CoinModuleLoader` now declares a `supportedCoins: CryptoCurrencyId[]` field, and a currency is supported when it appears in a registered loader's `supportedCoins`. The framework `setSupportedCurrencies` / `listSupportedCurrencies` / `isCurrencySupported` and the `EXPERIMENTAL_CURRENCIES` env are removed; `listSupportedCurrencies` / `isCurrencySupported` are now exported from `@ledgerhq/live-common/currencies` backed by the registry. Apps no longer maintain a supported-currencies list — registering the coin modules is what makes their currencies supported.
-
-## 2.38.0
-
-### Minor Changes
-
-- [#18030](https://github.com/LedgerHQ/ledger-live/pull/18030) [`b14d5cc`](https://github.com/LedgerHQ/ledger-live/commit/b14d5cc29cc75c6be2e565db3d4d0ab400cc56d9) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - refactor: unify aleo node endpoint env
-
-- [#18105](https://github.com/LedgerHQ/ledger-live/pull/18105) [`ec38133`](https://github.com/LedgerHQ/ledger-live/commit/ec38133ab6b2c18d329e1c78320b7c2a1f80fbfc) Thanks [@ishaba](https://github.com/ishaba)! - feat: cardano coin module api getValidators
-
-## 2.38.0-next.0
-
-### Minor Changes
-
-- [#18030](https://github.com/LedgerHQ/ledger-live/pull/18030) [`b14d5cc`](https://github.com/LedgerHQ/ledger-live/commit/b14d5cc29cc75c6be2e565db3d4d0ab400cc56d9) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - refactor: unify aleo node endpoint env
-
-- [#18105](https://github.com/LedgerHQ/ledger-live/pull/18105) [`ec38133`](https://github.com/LedgerHQ/ledger-live/commit/ec38133ab6b2c18d329e1c78320b7c2a1f80fbfc) Thanks [@ishaba](https://github.com/ishaba)! - feat: cardano coin module api getValidators
-
-## 2.37.0
-
-### Minor Changes
-
-- [#17648](https://github.com/LedgerHQ/ledger-live/pull/17648) [`5fc817a`](https://github.com/LedgerHQ/ledger-live/commit/5fc817a5ee316396a327e5b10eccd8314bfb2df5) Thanks [@hedi-edelbloute](https://github.com/hedi-edelbloute)! - Add Arc and Arc Testnet (Circle's USDC-native EVM L1, chainIds 5042 and 5042002)
-
-- [#17877](https://github.com/LedgerHQ/ledger-live/pull/17877) [`65f87d9`](https://github.com/LedgerHQ/ledger-live/commit/65f87d938ac4158e0ae706593d2a46561097f5a9) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - refactor: upgrade hedera utils with configOrCurrencyId param
-
-## 2.37.0-next.0
-
-### Minor Changes
-
-- [#17648](https://github.com/LedgerHQ/ledger-live/pull/17648) [`5fc817a`](https://github.com/LedgerHQ/ledger-live/commit/5fc817a5ee316396a327e5b10eccd8314bfb2df5) Thanks [@hedi-edelbloute](https://github.com/hedi-edelbloute)! - Add Arc and Arc Testnet (Circle's USDC-native EVM L1, chainIds 5042 and 5042002)
-
-- [#17877](https://github.com/LedgerHQ/ledger-live/pull/17877) [`65f87d9`](https://github.com/LedgerHQ/ledger-live/commit/65f87d938ac4158e0ae706593d2a46561097f5a9) Thanks [@mdomanski-ext-ledger](https://github.com/mdomanski-ext-ledger)! - refactor: upgrade hedera utils with configOrCurrencyId param
-
-<!-- changelog-pruned: older entries were removed to keep this file small. Full history is in `git log -p CHANGELOG.md` and in the GitHub release for each version. -->
+- [#98](https://github.com/LedgerHQ/ts-libs/pull/98) [`461d059`](https://github.com/LedgerHQ/ts-libs/commit/461d059638e47c2f73b7f9c214e42f330e67a0d1) Thanks [@gre-ledger](https://github.com/gre-ledger)! - Move the package from the ledger-live monorepo to ts-libs. No API change; the package stays
+  DEPRECATED and is still being sunset — see MIGRATION.md.
+  
+  The `exports` map now lists `.`, `./index`, `./env`, `./state`, `./lib/*` and `./lib-es/*`
+  explicitly, in place of the previous `./*` wildcard.

package/MIGRATION.md

@@ -0,0 +1,148 @@
+# Migrating off `@ledgerhq/live-env`
+
+> [!WARNING]
+> **`@ledgerhq/live-env` is deprecated.** Do not add definitions, do not add call sites.
+> This guide is how you take an existing one out.
+
+## Why
+
+The framework is fine; the injection is the problem. `injectDefinitions()` registers a global
+mutable singleton, and everything downstream inherits it:
+
+- every consumer of a shared library must inject, or `getEnv` throws
+- a value read through a global is invisible in the dependency graph — nothing tells you a library
+  needs it until it fails at runtime
+- it duplicates three mechanisms that already exist: feature flags, build-time constants, and
+  `process.env`
+
+## The four exits
+
+Every variable leaves by exactly one of these. Pick by asking what the value actually does, not by
+what is easiest to type.
+
+| The value…                 | Replacement                       | Why                              |
+| -------------------------- | --------------------------------- | -------------------------------- |
+| is togglable remotely      | **feature flag**                  | already remote, typed, audited   |
+| never varies at runtime    | **inline constant**               | the dependency leaves the graph  |
+| varies in CI / tests / dev | **`process.env` at the use site** | no registry, no injection        |
+| varies per app             | **passed in as a parameter**      | the app owns state, not the lib  |
+
+If two look plausible, prefer the one further down the table: it removes more machinery.
+If none fit, that is a signal worth raising, not a blocker.
+
+---
+
+### 1. Togglable remotely → feature flag
+
+A value someone wants to flip without a release is a feature flag. Often the flag already exists
+and the env var is just the fallback nobody deleted — check before writing a new one.
+
+```diff
+- import { getEnv } from "@ledgerhq/live-env";
+-
+- if (!feature?.enabled) return getEnv("ENABLE_THING").split(",");
+- return feature?.params?.things ?? null;
++ return feature?.params?.things ?? null;
+```
+
+Outside React, the flag reaches you through the config your composition root already builds — not
+through a second global.
+
+### 2. Never varies at runtime → inline constant
+
+If nothing calls `setEnv` on it and no bootstrap overrides it, it is a constant that has been
+paying registry rent for years.
+
+```diff
+- import { getEnv } from "@ledgerhq/live-env";
+- const version = () => getEnv("API_VERSION");
++ const API_VERSION = 2;
+```
+
+This is the exit that shrinks the dependency graph: the module stops importing the library at all.
+
+Two things make *every* variable look overridable, and neither should stop you: a bootstrap that
+loops `process.env` into `setEnvUnsafe`, and any debug UI that can set a variable by name. Those
+are generic escape hatches, not evidence that a value varies. Ask whether a *product* path sets it.
+
+### 3. Varies in CI / tests / dev → `process.env` at the point of use
+
+Read it where you need it and parse it there. No registry entry, no injection, no import ordering.
+
+```diff
+- import { getEnv } from "@ledgerhq/live-env";
+- setDecimalPlaces(getEnv("DECIMAL_PLACES"));
++ const decimalPlaces = Number.parseInt(process.env.DECIMAL_PLACES ?? "", 10);
++ setDecimalPlaces(Number.isNaN(decimalPlaces) ? 40 : decimalPlaces);
+```
+
+Keep the default at the use site, as above.
+
+> [!CAUTION]
+> **Do not fall back with `||`.** `Number(process.env.X) || 40` looks equivalent and is not: it
+> swallows a legitimate `0`, and `false` for booleans. `intParser` returns `0` for `X=0` today, so
+> `||` silently changes behaviour for anyone who set it. Test against `Number.isNaN`, or `??` over
+> an already-parsed value. This is the most likely way to introduce a bug while migrating.
+
+Where `process.env` is not populated the way it is under Node — a React Native app, a bundler
+target — use that platform's existing accessor. The point of the exit is unchanged: the value stops
+travelling through a singleton.
+
+### 4. Varies per app → passed in as a parameter
+
+The app knows things a library cannot. Take the value as an argument. Do not store it.
+
+Replacing `getEnv` with a module-level `let` and a `configure()` is the same anti-pattern one size
+down — still global, still mutable, still absent from the signature, still order-dependent at
+import time. Runtime state is the end app's responsibility; a library receives what it needs.
+
+```diff
+  // library
+- import { getEnv } from "@ledgerhq/live-env";
+-
+- export function fetchThing(id: string) {
+-   return request(`${getEnv("API_URL")}/things/${id}`);
+- }
++ export function fetchThing(ctx: { apiUrl: string }, id: string) {
++   return request(`${ctx.apiUrl}/things/${id}`);
++ }
+```
+
+Where several values travel together, group them into one context object threaded as the first
+argument rather than growing the parameter list.
+
+The signature is the whole point. A caller cannot forget the value, a test supplies a different one
+without touching global state, and two callers can use two different values at the same time —
+none of which a singleton allows.
+
+If the library already has a `setX()`/`configure()`, moving a variable into it is a shorter step
+than staying, but it is not the destination. Prefer the parameter.
+
+Two things to get right:
+
+- **A value the user can change is app state.** The library does not subscribe to it; the app
+  re-reads its own store and passes the current value on the next call.
+- **Migrate the whole bridge, not one key.** Where a setup function copies several variables into a
+  library, taking one of them out and leaving the call silently drops the rest.
+
+**Backend URLs deserve extra care.** Do not inline an endpoint where the `getEnv` used to be — that
+scatters one backend's address across every file that talks to it, which is the same mistake in a
+new shape. Resolve it once, in the app, and pass it down with the rest of the context.
+`_STAGING`/`_PROD` pairs are not two endpoints: they are one endpoint and an app-level choice of
+which URL to pass.
+
+---
+
+## While the burn-down runs
+
+- **Do not add a new definition.** A new value should be born in one of the four exits.
+- **Do not add a new call site**, including in tests. In a test, set the value the way the
+  production code will read it after the migration, not through `setEnv`.
+- Migrating a variable means removing its definition in the same PR. A definition with zero call
+  sites left is dead weight nobody will come back for.
+- **Check for dead ones first.** A definition with no call sites anywhere is a deletion, not a
+  migration.
+
+## Done
+
+`@ledgerhq/live-env` unpublished and deleted.

package/README.md

@@ -2,11 +2,9 @@
 
 > [!WARNING]
 > **Status: DEPRECATED** — `@ledgerhq/live-env` is being sunset. Do not add env var definitions and
-> do not add call sites. To take an existing one out, read
-> **[docs/configuration.md](https://github.com/LedgerHQ/ledger-live/blob/develop/docs/configuration.md)**.
-> It maps every kind of value to its home — a feature flag, an inline constant, `process.env` at
-> the point of use, the app's `.env` file, a bundler define, the app's settings slice, or a
-> parameter the caller passes in.
+> do not add call sites. To take an existing one out, read **[MIGRATION.md](./MIGRATION.md)**:
+> every variable exits as a feature flag, an inline constant, `process.env` at the point of use,
+> or a parameter the caller passes in.
 >
 > The package still works exactly as documented below until the last call site is gone.
 

package/lib/env.d.ts

@@ -3,26 +3,22 @@ export type { EnvDef, EnvDefs, EnvChange } from "./state";
 import type { EnvDef as EnvDefRecord } from "./state";
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and these parsers go with it. Parse and
- * default explicitly at the point of use instead — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * default explicitly at the point of use instead — see MIGRATION.md.
  */
 export declare const intParser: (v: any) => number | undefined;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and these parsers go with it. Parse and
- * default explicitly at the point of use instead — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * default explicitly at the point of use instead — see MIGRATION.md.
  */
 export declare const floatParser: (v: any) => number | undefined;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and these parsers go with it. Parse and
- * default explicitly at the point of use instead — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * default explicitly at the point of use instead — see MIGRATION.md.
  */
 export declare const boolParser: (v: unknown) => boolean | undefined;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and these parsers go with it. Parse and
- * default explicitly at the point of use instead — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * default explicitly at the point of use instead — see MIGRATION.md.
  */
 export declare const stringParser: (v: unknown) => string | undefined;
 type JSONValue = string | number | boolean | {
@@ -30,61 +26,57 @@ type JSONValue = string | number | boolean | {
 } | Array<JSONValue>;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and these parsers go with it. Parse and
- * default explicitly at the point of use instead — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * default explicitly at the point of use instead — see MIGRATION.md.
  */
 export declare const jsonParser: (v: unknown) => JSONValue | undefined;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and these parsers go with it. Parse and
- * default explicitly at the point of use instead — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * default explicitly at the point of use instead — see MIGRATION.md.
  */
 export declare const stringArrayParser: (v: unknown) => string[] | undefined;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and the registry it introspects goes with
- * it — see [docs/configuration.md](../../../docs/configuration.md).
+ * it — see MIGRATION.md.
  */
 export declare const getDefinition: (name: string) => EnvDefRecord<unknown> | undefined;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and the registry it introspects goes with
- * it — see [docs/configuration.md](../../../docs/configuration.md).
+ * it — see MIGRATION.md.
  */
 export declare const getAllEnvNames: () => string[];
 /**
- * @deprecated `@ledgerhq/live-env` is being sunset — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * @deprecated `@ledgerhq/live-env` is being sunset. See MIGRATION.md.
  */
 export declare const getAllEnvs: () => Record<string, unknown>;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset. Replace this read with a feature flag,
  * an inline constant, `process.env` at the point of use, or a value the caller passes in —
- * see [docs/configuration.md](../../../docs/configuration.md).
+ * see MIGRATION.md.
  */
 export declare function getEnv(name: string): any;
 /**
- * @deprecated `@ledgerhq/live-env` is being sunset — see
- * [docs/configuration.md](../../../docs/configuration.md).
+ * @deprecated `@ledgerhq/live-env` is being sunset. See MIGRATION.md.
  */
 export declare function getEnvDefault(name: string): any;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and the registry it introspects goes with
- * it — see [docs/configuration.md](../../../docs/configuration.md).
+ * it — see MIGRATION.md.
  */
 export declare const isEnvDefault: (name: string) => boolean;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset, and the registry it introspects goes with
- * it — see [docs/configuration.md](../../../docs/configuration.md).
+ * it — see MIGRATION.md.
  */
 export declare const getEnvDesc: (name: string) => string;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset. A value that has to change at runtime
  * belongs in a feature flag or in the app's own state, not in a global mutable singleton —
- * see [docs/configuration.md](../../../docs/configuration.md).
+ * see MIGRATION.md.
  */
 export declare function setEnv(name: string, value: unknown): void;
 /**
  * @deprecated `@ledgerhq/live-env` is being sunset. Read and parse the raw value where you
- * use it instead — see [docs/configuration.md](../../../docs/configuration.md).
+ * use it instead — see MIGRATION.md.
  */
 export declare const setEnvUnsafe: (name: string, unsafeValue: unknown) => boolean;
 //# sourceMappingURL=env.d.ts.map

package/lib/env.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"env.d.ts","sourceRoot":"","sources":["../src/env.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,iBAAiB,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AACrD,YAAY,EAAE,MAAM,EAAE,OAAO,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AAE1D,OAAO,KAAK,EAAE,MAAM,IAAI,YAAY,EAAE,MAAM,SAAS,CAAC;AAEtD;;;;GAIG;AACH,eAAO,MAAM,SAAS,MAAO,GAAG,KAAG,MAAM,GAAG,SAG3C,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,WAAW,MAAO,GAAG,KAAG,MAAM,GAAG,SAG7C,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,UAAU,MAAO,OAAO,KAAG,OAAO,GAAG,SAGjD,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,YAAY,MAAO,OAAO,KAAG,MAAM,GAAG,SACZ,CAAC;AAExC,KAAK,SAAS,GAAG,MAAM,GAAG,MAAM,GAAG,OAAO,GAAG;IAAE,CAAC,CAAC,EAAE,MAAM,GAAG,SAAS,CAAA;CAAE,GAAG,KAAK,CAAC,SAAS,CAAC,CAAC;AAE3F;;;;GAIG;AACH,eAAO,MAAM,UAAU,MAAO,OAAO,KAAG,SAAS,GAAG,SAOnD,CAAC;AAEF;;;;GAIG;AACH,eAAO,MAAM,iBAAiB,MAAO,OAAO,KAAG,MAAM,EAAE,GAAG,SAGzD,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,aAAa,SAAU,MAAM,KAAG,YAAY,CAAC,OAAO,CAAC,GAAG,SACA,CAAC;AAEtE;;;GAGG;AACH,eAAO,MAAM,cAAc,QAAO,MAAM,EAA2C,CAAC;AAEpF;;;GAGG;AACH,eAAO,MAAM,UAAU,QAAO,MAAM,CAAC,MAAM,EAAE,OAAO,CAA8B,CAAC;AAGnF;;;;GAIG;AACH,wBAAgB,MAAM,CAAC,IAAI,EAAE,MAAM,GAAG,GAAG,CAExC;AAED;;;GAGG;AACH,wBAAgB,aAAa,CAAC,IAAI,EAAE,MAAM,GAAG,GAAG,CAE/C;AAED;;;GAGG;AACH,eAAO,MAAM,YAAY,SAAU,MAAM,KAAG,OAG3C,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,UAAU,SAAU,MAAM,KAAG,MACwC,CAAC;AAEnF;;;;GAIG;AACH,wBAAgB,MAAM,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,OAAO,GAAG,IAAI,CAOzD;AAED;;;GAGG;AACH,eAAO,MAAM,YAAY,SAAU,MAAM,eAAe,OAAO,KAAG,OAajE,CAAC"}
+{"version":3,"file":"env.d.ts","sourceRoot":"","sources":["../src/env.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,iBAAiB,EAAE,OAAO,EAAE,MAAM,SAAS,CAAC;AACrD,YAAY,EAAE,MAAM,EAAE,OAAO,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AAE1D,OAAO,KAAK,EAAE,MAAM,IAAI,YAAY,EAAE,MAAM,SAAS,CAAC;AAEtD;;;GAGG;AACH,eAAO,MAAM,SAAS,MAAO,GAAG,KAAG,MAAM,GAAG,SAG3C,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,WAAW,MAAO,GAAG,KAAG,MAAM,GAAG,SAG7C,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,UAAU,MAAO,OAAO,KAAG,OAAO,GAAG,SAGjD,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,YAAY,MAAO,OAAO,KAAG,MAAM,GAAG,SACZ,CAAC;AAExC,KAAK,SAAS,GAAG,MAAM,GAAG,MAAM,GAAG,OAAO,GAAG;IAAE,CAAC,CAAC,EAAE,MAAM,GAAG,SAAS,CAAA;CAAE,GAAG,KAAK,CAAC,SAAS,CAAC,CAAC;AAE3F;;;GAGG;AACH,eAAO,MAAM,UAAU,MAAO,OAAO,KAAG,SAAS,GAAG,SAOnD,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,iBAAiB,MAAO,OAAO,KAAG,MAAM,EAAE,GAAG,SAGzD,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,aAAa,SAAU,MAAM,KAAG,YAAY,CAAC,OAAO,CAAC,GAAG,SACA,CAAC;AAEtE;;;GAGG;AACH,eAAO,MAAM,cAAc,QAAO,MAAM,EAA2C,CAAC;AAEpF;;GAEG;AACH,eAAO,MAAM,UAAU,QAAO,MAAM,CAAC,MAAM,EAAE,OAAO,CAA8B,CAAC;AAGnF;;;;GAIG;AACH,wBAAgB,MAAM,CAAC,IAAI,EAAE,MAAM,GAAG,GAAG,CAExC;AAED;;GAEG;AACH,wBAAgB,aAAa,CAAC,IAAI,EAAE,MAAM,GAAG,GAAG,CAE/C;AAED;;;GAGG;AACH,eAAO,MAAM,YAAY,SAAU,MAAM,KAAG,OAG3C,CAAC;AAEF;;;GAGG;AACH,eAAO,MAAM,UAAU,SAAU,MAAM,KAAG,MACwC,CAAC;AAEnF;;;;GAIG;AACH,wBAAgB,MAAM,CAAC,IAAI,EAAE,MAAM,EAAE,KAAK,EAAE,OAAO,GAAG,IAAI,CAOzD;AAED;;;GAGG;AACH,eAAO,MAAM,YAAY,SAAU,MAAM,eAAe,OAAO,KAAG,OAajE,CAAC"}