@metamask/remote-feature-flag-controller 1.0.0
The RemoteFeatureFlagController manages the retrieval and caching of remote feature flags
@metamask/remote-feature-flag-controller@1.0.0 was published on 2024-11-28. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^18.18 || >=20.
All @metamask/remote-feature-flag-controller versions · Permanent reference to 1.0.0 · Latest release
Package specifications
| Version | 1.0.0 |
|---|---|
| License declaration | (MIT OR Apache-2.0) |
| Published | 2024-11-28T19:50:44.134Z |
| Node.js requirement | ^18.18 || >=20 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 112.00 KiB |
| Published file count | 54 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./dist/index.cjs |
| Side effects declaration | false |
| Direct advisories | 0 |
| Resolved graph dependencies | 36 |
| Repository stars | 420 |
| Repository forks | 312 |
Install @metamask/remote-feature-flag-controller 1.0.0
npm install @metamask/remote-feature-flag-controller@1.0.0 pnpm add @metamask/remote-feature-flag-controller@1.0.0 yarn add @metamask/remote-feature-flag-controller@1.0.0
Runtime dependencies
- cockatiel ^3.1.2
- @metamask/utils ^10.0.0
- @metamask/base-controller ^7.0.2
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @metamask/base-controller@7.1.1 — direct
- @metamask/utils@10.0.1 — direct
- cockatiel@3.2.1 — direct
- @metamask/utils@11.12.1 — indirect
- immer@9.0.21 — indirect
- @ethereumjs/tx@4.2.0 — indirect
- @metamask/superstruct@3.4.1 — indirect
- @noble/hashes@1.8.0 — indirect
- @scure/base@1.2.6 — indirect
- @types/debug@4.1.13 — indirect
- debug@4.4.3 — indirect
- pony-cause@2.1.11 — indirect
- semver@7.8.5 — indirect
- uuid@9.0.1 — indirect
- @metamask/scure-bip39@2.1.1 — indirect
- @types/lodash@4.17.27 — indirect
- lodash@4.18.1 — indirect
- @ethereumjs/common@3.2.0 — indirect
- @ethereumjs/rlp@4.0.1 — indirect
- @ethereumjs/util@8.1.0 — indirect
- ethereum-cryptography@2.2.1 — indirect
- @types/ms@2.1.0 — indirect
- ms@2.1.3 — indirect
- @noble/hashes@1.3.3 — indirect
- @scure/base@1.1.9 — indirect
- crc-32@1.2.2 — indirect
- micro-ftch@0.3.1 — indirect
- @noble/curves@1.4.2 — indirect
- @noble/hashes@1.4.0 — indirect
- @scure/bip32@1.4.0 — indirect
- @scure/bip39@1.3.0 — indirect
- @noble/hashes@1.4.0 — indirect
- @noble/hashes@1.4.0 — indirect
- @scure/base@1.1.9 — indirect
- @noble/hashes@1.4.0 — indirect
- @scure/base@1.1.9 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- https://registry.npmjs.org/%40metamask%2Fremote-feature-flag-controller/1.0.0 — retrieved 2026-10-31T05:50:28.480Z
- https://api.deps.dev/v3/systems/npm/packages/%40metamask%2Fremote-feature-flag-controller/versions/1.0.0 — retrieved 2026-10-31T05:50:28.881Z
- https://api.deps.dev/v3/systems/npm/packages/%40metamask%2Fremote-feature-flag-controller/versions/1.0.0:dependencies — retrieved 2026-10-31T05:50:28.918Z
- https://api.deps.dev/v3/projects/github.com%2FMetaMask%2Fcore — retrieved 2026-10-31T03:49:41.657Z