chore(deps): no lockfile is committed, so installs resolve different dependency versions each time
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, github-actions, javascript, nodejs
- Domain
- build-system, ci-cd
Research direction
Start at the repo root: check package.json for the package manager in use and confirm no bun.lock or package-lock.json is present or gitignored. Run the install once (bun install) and commit the generated lockfile, then look in .github/workflows for the install step and switch it to a frozen-lockfile install so CI fails when the lockfile drifts. Done means the lockfile is committed at the root and a frozen-lockfile install passes in CI with existing tests still green.
Written by the indexing model from the issue text.
Description
Problem
flisk-sh/analytics has no lockfile (bun.lock, package-lock.json or similar) at the repo root. Two contributors, or CI and a laptop, can install different dependency versions, and a new transitive release can break a build that worked yesterday. Sibling repos such as flisk-sh/chat commit bun.lock.
Repro:
gh api repos/flisk-sh/analytics/contents --jq '.[].name' | grep -iE 'lock' || echo "no lockfile"
# no lockfile
Root Cause Analysis
Dependencies were installed locally but the generated lockfile was never committed (or is ignored), so installs resolve the newest matching versions each time.
TDD Fix Plan
- RED: Add a CI step (or test) that fails when no lockfile exists, and when
install --frozen-lockfilewould change it.
GREEN: Run the install once, commit the lockfile.
REFACTOR: None expected.
Acceptance Criteria
- A lockfile is committed at the repo root
- Frozen-lockfile install succeeds
- All new tests pass
- Existing tests still pass
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No 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 flisk-sh/analytics
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
All issues in flisk-sh/analytics
Similar issues
-
chore cloudflare-workers consistency d1 difficulty: easy documentation dx enhancement good first issue help wanted hygiene javascript maintenance priority: P3 seo
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MattiaPARRINELLO/backstage#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·