-
Notifications
You must be signed in to change notification settings - Fork 152
Open
Description
Summary
@ruvector/rvdna@0.1.1 declares five platform-specific optional dependencies in package.json, but none of them have been published to npm. This means isNativeAvailable() always returns false and the native-only functions (fastaToRvdna, readRvdna) are unusable on every platform.
Missing packages
All five are listed as optionalDependencies at version 0.1.0 but return 404 from the npm registry:
| Package | Status |
|---|---|
@ruvector/rvdna-linux-x64-gnu |
Not published |
@ruvector/rvdna-linux-arm64-gnu |
Not published |
@ruvector/rvdna-darwin-x64 |
Not published |
@ruvector/rvdna-darwin-arm64 |
Not published |
@ruvector/rvdna-win32-x64-msvc |
Not published |
Impact
- The pure JS fallbacks for
encode2bit,decode2bit,translateDna, andcosineSimilaritywork fine. fastaToRvdna()throws"requires native bindings"on all platforms.readRvdna()throws"requires native bindings"on all platforms.- The
.rvdnabinary format is effectively inaccessible from Node.js until these are published.
Steps to reproduce
npm install @ruvector/rvdna
node -e "const r = require('@ruvector/rvdna'); console.log('native:', r.isNativeAvailable())"
# Output: native: falseExpected
npm install @ruvector/rvdna should pull in the correct platform binary (e.g. @ruvector/rvdna-linux-x64-gnu on Linux x64 glibc) and isNativeAvailable() should return true.
Environment
@ruvector/rvdna@0.1.1- Linux x86_64 (glibc), Node.js v24.13.0
- npm 11.x
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels