feature: support for bun.lock
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 788
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Bun's new lockfile, as of version 1.2, is JSONC instead of binary. It would be cool to be able to convert from bun.lock to package-lock.json.
https://bun.sh/blog/bun-v1.2#introducing-bun-lock
Bun currently doesn't have a bun audit (although may soon) so one workaround would be converting the lockfile first and then using npm audit. Bun does support creating a yarn.lock file but it seems to generate an older version and I've had issues with it working with yarn audit (particularly due to the way it handles overrides - see this comment, although that's from before the jsonc lockfile so it may have changed).
Regardless of audit support, it seems like it'd be a nice addition to synp to be able to go to/from bun.lock
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading synp's existing lockfile conversion paths and the Bun 1.2 lockfile details linked in the issue. Determine how bun.lock should convert to package-lock.json and back, including the stated audit use case. Done means both conversion directions are supported and verified against representative Bun lockfiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100