zeekay 9fae041bb1 State a version once
A version written into a manifest is written into every manifest that wants it,
which is how eslint came to exist in a hundred and four forms across this estate
and how a package came to resolve twice at run time. The catalog moves the number
out of the manifest: a manifest names the package, the workspace names the
version.

Four are held below their latest because the newer release cannot be used, and
the reason is recorded rather than the version alone: @noble/hashes 2 renamed
every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package
that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels
3 points its types condition at the bundle.
2026-08-29 13:46:56 -07:00
2026-06-28 20:54:54 -07:00
2024-07-16 01:35:02 +10:00
2026-08-04 16:51:28 -07:00
2024-07-16 01:35:02 +10:00
2026-08-29 13:46:56 -07:00
2026-06-28 20:54:55 -07:00

lux-sign

@luxwallet/lux-sign

Getting Started

install by npm, yarn etc

npm i -S @luxwallet/lux-sign
# or
yarn add @luxwallet/lux-sign

APIs

Signature

For every use cases, we provide two kinds of implementations: by Javascript and by WebAssembly. for example:

import * as SignWasm from '@luxwallet/lux-sign/es/sign-wasm-lux'

Development

Build

# build for web
npm run build:umd

# build for nodejs/react-native
npm run build:cjs

Test

We use jest, ts-jest to test source code, in all spec files, we import members to be test from ./src DIRECTLY

npm run test
S
Description
lux custom node module
Readme MIT
55 KiB
Languages
SVG 100%