@solana-mobile/mobile-wallet-adapter-protocol-web3js 2.2.2

A convenience wrapper that enables you to call Solana Mobile Stack protocol methods using objects from @solana/web3.js

@solana-mobile/mobile-wallet-adapter-protocol-web3js@2.2.2 was published on 2025-06-13. Its manifest declares 3 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @solana-mobile/mobile-wallet-adapter-protocol-web3js versions · Permanent reference to 2.2.2 · Latest release

Package specifications

Version2.2.2
License declarationApache-2.0
Published2025-06-13T21:58:52.027Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size48.59 KiB
Published file count21
Package typemodule
ES module entrylib/esm/index.js
Default entrylib/cjs/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies72
Repository stars329
Repository forks161

Install @solana-mobile/mobile-wallet-adapter-protocol-web3js 2.2.2

npm install @solana-mobile/mobile-wallet-adapter-protocol-web3js@2.2.2
pnpm add @solana-mobile/mobile-wallet-adapter-protocol-web3js@2.2.2
yarn add @solana-mobile/mobile-wallet-adapter-protocol-web3js@2.2.2

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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