-
Notifications
You must be signed in to change notification settings - Fork 16
doc: update instructions for running on Mac #547
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have some typos/suggestions on the docs, and I checked all the npm commands work fine still. Feel free to resolve the "works" comments, that was just for me keeping track as I tested.
OK, I think that covers everything you mentioned. |
I think you missed some comments that were "folded up" |
So right you are. Hopefully I have taken care of them now. |
Oh, somehow the change triggered lint. I will take out space and make lint happy. |
* doc: update instructions for running on Mac * doc: fix typos from review * doc: oops more typos from review * doc: and now make lint happy * doc: and fix punctuation order * doc: remove ugly space and fix lint
By submitting this PR, I am indicating to the Numberscope maintainers that I have read and understood the contributing guidelines and that this PR follows those guidelines to the best of my knowledge. I have also read the pull request checklist and followed the instructions therein.
This PR was created entirely on a Mac, to make sure that the frontscope is looking OK on Safari. There were various installation bumps, and just a few code changes -- so this PR is mostly documentation of everything I did. Once I got it running, frontscope looked great on Safari, so fortunately nothing substantive to do there. I did not actually get Docker running on MacOS or run the e2e tests, mostly because I figured we don't have MacOS snapshots so it would be pretty meaningless anyway.
But this PR does need checking, running, and e2e tests on linux by a reviewer to make sure it didn't disrupt anything for our standard development and execution environment.