`@tensorflow/tfjs-node` installation issue
@nileshau-afk is already working on this.
Since Oct 9, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- node.js, tensorflow, typescript
- Domain
- build-system, devtools
Research direction
Start by reproducing the npm installation warnings for @tensorflow/tfjs-node and tracing which package in its dependency tree brings in the deprecated dependencies listed in the issue. The issue names no manifest or test, so inspect the package and dependency configuration to identify the source. Done means the installation no longer pulls in the reported deprecated dependencies, with installation behavior verified.
Written by the indexing model from the issue text.
Description
@tensorflow/tfjs-node installation pulls in multiple deprecated dependencies
Description
When installing the latest @tensorflow/tfjs-node, npm reports several deprecated dependencies in the dependency tree.
For example, during installation I receive:
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: This package is no longer supported.
<img width="1421" height="263" alt="Image" src="https://github.com/user-attachments/assets/ff66deba-0715-45a2-8bde-5d3fd4fd15be" />
- Dominant language
- TypeScript
- Stars
- 19.2k
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tensorflow/tfjs
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tensorflow/tfjs#8754 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
tensorflow/tfjs#8753 ·
-
Review argparse dependency bringing in sprintf-js CVE-2026-97058Possibly taken @Varun-S10 claimed this 19 days ago. Opentype:others
Difficulty 4/5 3-5 days Newbie friendliness 22/100
tensorflow/tfjs#8749 · 1 assignee ·
-
The package tfjs-node is not working in version 26.8.1 of NodeMay be free again @nileshau-afk claimed this 57 days ago, and no pull request is open. Opencomp:node.js type:bug
tensorflow/tfjs#8746 · 4 comments · 1 reaction · 1 assignee ·
-
I'm getting these npm errors while trying to install @tensorflow/tfjs-nodeMay be free again @Varun-S10 claimed this 87 days ago, and no pull request is open. Openstat:awaiting tensorflower type:build/install type:support
tensorflow/tfjs#8740 · 4 comments · 1 reaction · 1 assignee ·
Similar issues
-
content triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 83/100
BraveOPotato/NoSignups#2348 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
code-yeongyu/oh-my-openagent#12784 ·
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MomsBloomOrg/momsbloom-resources#84 ·
Maintainers usually reply within 1 day