Skip to content

Commit 3ec136b

Browse files
committed
Add MX arm64 mac dev setup notes to README
1 parent 5016e55 commit 3ec136b

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

README.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,13 @@ To get started:
2121

2222
* Clone this repo.
2323
* `npm install`
24+
* On an arm64 Mac, you may see a Puppeteer error saying "The chromium binary is not available for arm64". See https://github.com/puppeteer/puppeteer/issues/6622 for more details. As a quick fix you can run `export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true` and then re-run npm install (you may need to delete node_modules first). In this case, the integration tests won't work but that's rarely important for local development.
2425
* For pure UI development
2526
* Run `npm start` to start the UI along with a backing [httptoolkit server](https://github.com/httptoolkit/httptoolkit-server).
26-
* Open [`localhost:8080`](http://localhost:8080) to view the UI
27+
* On an arm64 Mac, this may not work. You can run the server in development mode locally though (jump to the next section).
28+
* Open [`localhost:8080`](http://localhost:8080) to view the UI.
2729
* To develop the UI & server together
2830
* Start [a server](https://github.com/httptoolkit/httptoolkit-server) locally
2931
* Run `npm run start:web` to start the UI without running a separate HTTP Toolkit server
3032
* Open [`localhost:8080`](http://localhost:8080) to view the UI
31-
* `npm test` - run the tests (not many yet, but more are very welcome!)
33+
* `npm test` - run the tests

0 commit comments

Comments
 (0)