mirror of
https://github.com/pezkuwichain/pezkuwi-extension.git
synced 2026-10-26 21:39:52 +00:00
Kurdistan Tech Ministry
23bd90e7a3
Clears the Dependabot alerts that can be fixed inside the ranges the packages already declare, and drops one dependency nothing used. - Transitive bumps within declared ranges: axios, bn.js, undici, tar, postcss, minimatch, picomatch, brace-expansion, fast-uri, js-yaml, lodash, ws, ip-address, node-forge, follow-redirects, form-data, http-proxy-middleware, launch-editor, nanoid, qs, rollup, shell-quote, websocket-driver, flatted, colord, json5, browserslist. - styled-components 6.3.8 -> 6.5.3 (pulled by @pezkuwi/react-identicon and react-qr); 6.5 no longer pins postcss 8.4.49. - Remove extract-loader from packages/extension: no webpack config or source references it, and it was the only path to babel 6, babel-traverse and browserslist 3. What ships changes in two modules only. Built before and after, with build paths normalised: content.js is byte-identical; page.js and background.js differ in bn.js (5.2.2 -> 5.2.3); extension.js differs in bn.js and axios (1.13.4 -> 1.20.0, reached only through @zondax/ledger-substrate). Every other difference is the minifier renaming identifiers. No @pezkuwi/* package, wasm-crypto or bip39 code changes. Left for a change in @pezkuwi/dev, where they come from: webpack-dev-server 4 and what it pulls (webpack-dev-middleware, qs 6.14, uuid 8, node-forge), got 9 via gh-release, serialize-javascript 6 via terser-webpack-plugin, minimatch 9.0.3 via @typescript-eslint 6. All build or local-dev tooling. elliptic has no patched release; it arrives through crypto-browserify, the webpack crypto fallback. lint and test give the same result before and after this change; both were already failing on main (41 lint errors, 19 of 61 tests), hidden by continue-on-error in pr-any.yml.
Pezkuwi Extension
A browser extension for PezkuwiChain that injects a @pezkuwi/api Signer into a page, along with any associated accounts, allowing for use by any dapp. This is an implementation of a PezkuwiChain browser signer.
Developed by Dijital Kurdistan Tech Institute
Overview
This extension manages accounts and allows the signing of transactions with those accounts for the PezkuwiChain network.
Installation
- Chrome / Chromium / Brave / Edge: Install from the Chrome Web Store
- Firefox: build from source (see Development); a Firefox Add-ons listing is coming soon
Documentation
Find out more about how to use the extension as a Dapp developer in the Pezkuwi Extension Documentation
Development
Prerequisites
- Node.js >= 18.14
- Yarn 4.x (via corepack)
Building from Source
- Enable corepack:
corepack enable - Install dependencies:
yarn install - Build for Chrome:
yarn build:chrome - Build for Firefox:
yarn build:ff
Loading the Extension
Chrome:
- Go to
chrome://extensions/ - Enable "Developer mode"
- Click "Load unpacked" and select
packages/extension/build
Firefox:
- Go to
about:debugging#addons - Check "Enable add-on debugging"
- Click "Load Temporary Add-on" and select
packages/extension/build/manifest.json
Packages
- extension - Main entry point with injection and background logic
- extension-ui - UI components for the popup
- extension-dapp - Wrapper for dapps to work with injected objects
- extension-inject - Wrapper for extension developers to inject their extension
For Dapp Developers
Use the @pezkuwi/extension-dapp package to integrate with this extension or any compatible extension.
import { web3Enable, web3Accounts } from '@pezkuwi/extension-dapp';
// Enable the extension
const extensions = await web3Enable('My Dapp');
// Get all accounts
const accounts = await web3Accounts();
Links
- Website: https://pezkuwichain.io
- Documentation: https://docs.pezkuwichain.io
- GitHub: https://github.com/pezkuwichain
- API Docs: https://js.pezkuwichain.app
License
Apache-2.0
Author
Dijital Kurdistan Tech Institute