Update deps to install on Apple M1 #58
Open
Conversation
This file contains 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
I noticed the client used Yarn to lock deps, while the server used npm, so I tried deleting them both and seeing what running `yarn run setup` would autogenerate. It only created a yarn.lock file in the root dir, so it seems like these two files aren't being used and can be deleted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Per #56, I was having trouble running
yarn run setupon my Apple M1 machine. This PR updates three npm packages that needed newer versions to install on an M1.Note that I haven't tried running the app locally (per #57), so these changes could potentially be breaking. Please let me know if there are any tests I can run first 😄
Thanks everyone!