chore(deps): no lockfile is committed, so installs resolve different dependency versions each time

Open Beginner friendly
#16 0 comments 0 reactions 0 assignees View on GitHub

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

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

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

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

  1. RED: Add a CI step (or test) that fails when no lockfile exists, and when install --frozen-lockfile would 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flisk-sh/analytics

All issues in flisk-sh/analytics

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.