Register bun.lock as JSON
#7193
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
This comment was marked as outdated.
This comment was marked as outdated.
|
@lildude currently the search shows 1.7k files matching. Does that meet the popularity criteria? 
|
|
yay |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Bun recently added a text lockfile called
bun.lock(https://bun.sh/blog/bun-lock-text-lockfile) and it will soon become default.Checklist:
Although
bun.lockofficially uses JSONC, this PR sets it to standard JSON. Bun only relies on the trailing comma feature, which JSON happens to support without errors. The main reason to use standard JSON is that it provides better syntax highlighting on GitHub (#6197)