Skip to content

Document that bruno-cli can be installed with Homebrew#80

Open
tkegan wants to merge 1 commit into
usebruno:mainfrom
tkegan:patch-1
Open

Document that bruno-cli can be installed with Homebrew#80
tkegan wants to merge 1 commit into
usebruno:mainfrom
tkegan:patch-1

Conversation

@tkegan

@tkegan tkegan commented Apr 24, 2026

Copy link
Copy Markdown

This PR if accepted documents that the bruno-cli can be installed using the Homebrew package manager popular among Mac developers and sometimes used by Linux developers. I suggest it because it automatically takes care of the Node dependency.

@ganesh-bruno

Copy link
Copy Markdown
Collaborator

Hi, @tkegan

Have you done installation of Bruno CLI using homebrew?
Bruno CLI can be install only with node package managers (ex: npm, yarn)

Let me know if I missed anything.

@tkegan

tkegan commented Apr 28, 2026

Copy link
Copy Markdown
Author

I have, works just fine

tkegan@brick:~/Documents/Personal/Invoicing/$ date
Tue Apr 28 07:57:47 AM EDT 2026
tkegan@brick:~/Documents/Personal/Projects/Invoicing$ brew leaves
bruno-cli
cloc
composer
git
mariadb
php
yarn
tkegan@brick:~/Documents/Personal/Projects/Invoicing$ cd test/api
tkegan@brick:~/Documents/Personal/Projects/Invoicing/test/api$ bru run --env "Local Testing"
Malformed Request Errors/Read client errors when id is not int (400 Bad Request) - 22 ms
Assertions
   ✓ res.status: eq 400
   ✓ res.body: eq The client must be specified as an integer
Malformed Request Errors/Modify client errors when id is not specified (400 Bad Request) - 2 ms
Assertions
   ✓ res.status: eq 400
   ✓ res.body: eq You must specify the client to modify via the id param
Malformed Request Errors/Modify client errors when id is not int (400 Bad Request) - 2 ms
Assertions
   ✓ res.status: eq 400
   ✓ res.body: eq You must specify the client to modify via the id param

@tkegan

tkegan commented Apr 28, 2026

Copy link
Copy Markdown
Author

Thinking about this a bit more, perhaps the folks behind bruno would rather not support installs via methods other than node package managers but would still be open to mentioning that other methods might work for users with other workflows. I'm happy to rework my suggestion if this is the case.

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