mirror of
https://github.com/pezkuwichain/pezkuwi-extension.git
synced 2026-11-04 08:31:06 +00:00
Satoshi Qazi Muhammed
71e20f843d
- extension-dapp and extension-inject had the manifest the build writes into build/ committed as their source manifest (main ./build/cjs/index.js, an exports map into ./build/). They are back in the source form of the upstream manifests; the build generates those fields itself. - Dependencies between the packages were workspace:*, and the build copies them into the published manifest as they are: @pezkuwi/extension-base 0.62.19 on npm depends on "@pezkuwi/extension-chains": "workspace:*" and cannot be installed. They are exact versions, as upstream has them; yarn still links the workspaces. - @pezkuwi/* common dependencies ^14.0.26 and api dependencies ^16.5.37. These carry wasm-crypto 7.5.20, where ed25519, secp256k1, derivation and bip39 are implemented; 7.5.18 shipped them as "not yet implemented" stubs. The root resolutions that forced 14.0.25, 16.5.36 and wasm-crypto 7.5.18 onto the tree are removed; every @pezkuwi package resolves to a single version without them. - @pezkuwi/dev ^0.85.12. - One version for everything: the packages were at 0.62.20, the extension package at 0.62.23, the root at 0.62.24 and the browser manifests at 0.62.26. All are 0.62.27, above every version on npm and in the stores.
@polkadot/extension-base
Functions, classes and other utilities used in @polkadot/extension. These include:
- background script handlers,
- message passing,
- scripts injected inside pages.
They are primarily meant to be used in @polkadot/extension, and can be broken without any notice to cater for @polkadot/extension's needs.
They are exported here if you wish to use part of them in the development of your
own extension. Don't forget to add process.env.EXTENSION_PREFIX to separate
ports and stores from the current extension's ones.