Skip to content

chore: remove stray package-lock.json from openfusion/ package dir - #123

Open
shrdgn wants to merge 1 commit into
mainfrom
claude/rm-stray-package-lock
Open

chore: remove stray package-lock.json from openfusion/ package dir#123
shrdgn wants to merge 1 commit into
mainfrom
claude/rm-stray-package-lock

Conversation

@shrdgn

@shrdgn shrdgn commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Summary

  • Removes openfusion/package-lock.json, an empty npm lockfile ({"packages": {}}) that was accidentally committed inside the Python package directory by a manual, out-of-band commit (ef521ea, "changes") outside the normal PR/CI flow.
  • It's unrelated to the real UI lockfile at web/package-lock.json (which web-build CI already keys its npm cache on) and serves no purpose where it sits.
  • Documents the cleanup in CHANGELOG.md.

Why it matters

A stray, empty lockfile inside openfusion/ is confusing to anyone browsing the package directory — it looks like a second, out-of-sync Node project living inside the Python package, when nothing in the repo actually installs from it (web/ is the only real npm project). Small, zero-risk cleanup.

Test plan

  • pytest -q — unaffected (no Python source touched)
  • ruff check .
  • Confirmed no tooling references openfusion/package-lock.json (grep -r across workflows, Dockerfile, pyproject.toml, Makefile — no hits)

Found via an automated repo-quality review.


Generated by Claude Code

An empty npm lockfile ({"packages": {}}) was accidentally committed inside
the Python package directory by a manual commit outside the normal PR/CI
flow. It's unrelated to the real UI lockfile at web/package-lock.json and
serves no purpose.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants