x-randomvalues read one export from react-native, NativeModules, and
took its types from the deprecated @types/react-native, which depends
on react-native itself: react-native 0.83, metro 0.83 and with them
image-size (open advisory, fixed only in 2.x, which metro 0.83 does not
accept). The two native modules it looks for are now declared in
src/react-native-modules.d.ts; the casts to RNExt are gone and each
module is checked before use. The published react-native.d.ts does not
reference react-native, and react-native/metro leave the dependency
tree.
braces resolves to @pezkuwi/braces 3.0.4: braces 3.0.3, the latest upstream release, has an open advisory with no fixed version (CVE-2026-93687, stack exhaustion through deeply nested patterns); the fork rejects nesting deeper than maxDepth (500) with a SyntaxError.
- @pezkuwi/dev, dev-test, dev-ts ^0.86.3
- rethrown errors carry the original as `cause` (hw-ledger, address decode)
- optional chain in isEthereumAddress, includes() in bip39 validation
- logger calls the lazy formatter through a typed function
- x-global: an assertion to the type the value already has removed,
with the comment and directive that explained it
- type-only re-exports of modules that emit no JavaScript
- disable directives renamed for the new rule names, or removed where
the rule no longer reports
The deno step mapped every package to https://deno.land/x/pezkuwi/..., which
never existed (nor does @pezkuwi on JSR): it was red on every run, hidden by
continue-on-error. Decided 2026-10-07: no Deno build. The src/mod.ts entry
points (imported by nothing else, and the switch that makes the build emit
build-deno/), the import maps, the deno script and the CI step are removed.
The npm packages are unchanged; Deno users can import them as npm:.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- 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
Satoshi Qazi Muhammed