sdk-ts/package-lock.json is stale; npm install rewrites it (0.2.3->0.5.7)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- node.js, typescript
- Domain
- build-system
Research direction
In sdk-ts/, compare package-lock.json with package.json; start by running npm install and inspect the lockfile changes. Regenerate and commit only sdk-ts/package-lock.json, then verify a fresh npm ci leaves it byte-identical and the test-ts CI job passes.
Written by the indexing model from the issue text.
Description
Severity: Low
Where: tokenjam sub-repo, sdk-ts/package-lock.json.
Observed: running npm install in sdk-ts/ (as the CI test-ts job does) rewrites sdk-ts/package-lock.json, bumping a version from 0.2.3 to 0.5.7. The committed lockfile is therefore STALE relative to package.json: a clean install does not reproduce it. Surfaced this session when a worker ran the test-ts check and had to discard the unrequested lockfile churn before committing an unrelated UI change.
Why it matters: every contributor who runs npm install gets a spurious, unrelated lockfile diff they must remember to discard (easy to accidentally sweep into a PR); and CI may be resolving a different dependency tree than the committed lockfile claims, defeating the point of pinning.
Fix direction: regenerate sdk-ts/package-lock.json from the current package.json in a dedicated commit (npm install, commit only the lockfile), confirm a subsequent clean npm install / npm ci leaves it unchanged, and confirm the test-ts CI job passes against it.
Done when: a fresh npm ci in sdk-ts/ succeeds and leaves package-lock.json byte-identical (no diff), on CI and locally.
- Dominant language
- Python
- Stars
- 122
- Forks
- 35
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 8
Getting set up
- Ships a 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 Metabuilder-Labs/tokenjam
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#786 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Metabuilder-Labs/tokenjam#759 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Metabuilder-Labs/tokenjam#728 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#591 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Metabuilder-Labs/tokenjam#332 ·
Maintainers usually reply within 1 day
All issues in Metabuilder-Labs/tokenjam
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ansys/pyansys-common-mcp#213 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
freedomofpress/dangerzone#1594 ·
Maintainers usually reply within 3 days
-
priority:P1 status:in-review type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
randomparity/kdive#3317 · 1 comment ·
Maintainers usually reply within 1 day
-
area:ci
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mesonbuild/meson#16281 ·
Maintainers usually reply within 1 day