-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Is bun install
ready yet?
#2450
Comments
Can #1372 be added to this list? It's not exactly with |
Can #2626 be added to this list |
Bug that you might want to add to the list: #2653 |
I'm a bit confused on the 1.0 release being announced and this issue still being open (implying bun install is not recommended for production use). |
Is there a public programmatic API? |
Request to consider #4944 into this list 🙏 |
Request to consider #5370 as well 🙏 |
Request to consider #643 into this list |
Another to consider to match npm behavior: Run |
Going to close this issue since this was meant as a pre-1.0 tracking issue. We do plan to implement all of these bugs/features. Closing because this issue would just be a list of every issue related to |
@Electroid might want to make sure the tag is applied to all posts linked in the main post. E.G. #2449 does not have a |
Almost! This is a tracking issue for when
bun install
is ready for production use.Features:
trustedDependencies
inpackage.json
#2073bun install
#1609bun run --workspaces
#5207bun run --workspace
#2232package.json
#2448bun install
support on Windows #2449Bugs:
exports
ignores some conditions (@astrojs/compiler
breaking) #2357Flags:
--save-dev
/-d
bun install <pkg> {--d|--optional}
#1819-D
as an alias for--development
inbun add
(in addition to-d
) #1931--peer
bun add --peer <pkg>
#1820The text was updated successfully, but these errors were encountered: