Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-added Bun lockfile #54

Merged
merged 2 commits into from
Feb 11, 2025
Merged

Re-added Bun lockfile #54

merged 2 commits into from
Feb 11, 2025

Conversation

NuroDev
Copy link
Member

@NuroDev NuroDev commented Feb 11, 2025

This PR fixes a small regression as part of #53 where the Bun lockfile was deleted.

Additionally this updates the README.md to rename bun.lockb to bun.lock since from here on out we will be using the text based lockfile.

@NuroDev NuroDev requested a review from colodenn February 11, 2025 14:23
@NuroDev NuroDev self-assigned this Feb 11, 2025
@NuroDev NuroDev enabled auto-merge (squash) February 11, 2025 14:24
Copy link

Released an experimental package:

bun add ronin@ben-ron-1099-experimental-73

This package will be removed after the pull request has been merged.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

@NuroDev NuroDev merged commit 8518f60 into main Feb 11, 2025
5 checks passed
@NuroDev NuroDev deleted the ben/ron-1099 branch February 11, 2025 14:25
@@ -58,7 +58,7 @@ bun link ronin

If your project is not yet compatible with [Bun](https://bun.sh), feel free to replace all of the occurances of the word `bun` in the commands above with `npm` instead.

You will just need to make sure that, once you [create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request#creating-the-pull-request) on the current repo, it will not contain a `package-lock.json` file, which is usually generated by npm. Instead, we're using the `bun.lockb` file for this purpose (locking sub dependencies to a certain version).
You will just need to make sure that, once you [create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request#creating-the-pull-request) on the current repo, it will not contain a `package-lock.json` file, which is usually generated by npm. Instead, we're using the `bun.lock` file for this purpose (locking sub dependencies to a certain version).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great catch!

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.

4 participants