- main/module/types/exports/browser/react-native/sideEffects back to the
upstream source form (they held the build's rewritten copies)
- @pezkuwi/dev ^0.85.12; util-crypto on @pezkuwi/wasm-crypto and wasm-util
^7.5.20 (the first complete wasm-crypto) and on @noble/curves ^1.9.7 and
@noble/hashes ^1.8.0, the versions whose current APIs it now uses
- resolutions: only typescript, as upstream; the pins that held the whole
tree to wasm 7.5.17 are gone
- every package at 14.0.26 (npm had 14.0.25, this tree said 14.0.22/23), with
the internal dependencies at the same version
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The root resolutions pointed @pezkuwi/scure-sr25519 at
portal:/home/mamostehp/pezkuwi-wasm/packages/scure-sr25519, a directory
that only existed on the machine 14.0.25 was published from. Everywhere
else `yarn install` stops with "Manifest not found", so this repository
could not be installed, built or tested, and the PR workflow had never run.
util-crypto already asks for ^0.2.1, which is on npm; its lib/ is identical
to packages/scure-sr25519 in pezkuwi-wasm (same "bizinikiwi" signing
context). Dropping the resolution resolves it there.
With this, install, lint and test run. They are not green yet: 161 of
3014 tests fail, most of them on @pezkuwi/wasm-crypto 7.5.17 stubs
(secp256k1, ed25519, scrypt, bip39Generate "not yet implemented"), which
pezkuwi-wasm#2 fixes as 7.5.19. That, the remaining failures and the
continue-on-error in pr-any.yml follow once 7.5.19 is published.
- Author: Dijital Kurdistan Tech Institute <dev@pezkuwichain.io>
- Fixed Uint8Array type errors in test files
- Added @types/react-native devDependency for x-randomvalues
- Added @pezkuwi/hw-ledger devDependency for networks tests
- Added @pezkuwi/x-randomvalues devDependency for util tests
- Updated all internal dependencies to 14.0.12
