Skip to content
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

Use yarn instead of npm #706

Merged
merged 13 commits into from
Jun 28, 2019
Merged

Use yarn instead of npm #706

merged 13 commits into from
Jun 28, 2019

Conversation

toolness
Copy link
Collaborator

@toolness toolness commented Jun 27, 2019

Aside from somehow being orders of magnitude faster than npm, it also makes it easier to install into arbitrary directories, which is especially useful for potentially getting around a very strange docker bug on Johanna's system.

Notes

To do

  • Fix broken tests.
  • Replace all mentions/uses of npm with 'yarn`.
  • Mention yarn as a dependency in README.md.
  • Add a comment about why we're installing node modules to /node_modules/ during development.

@toolness toolness marked this pull request as ready for review June 28, 2019 13:54
@toolness toolness merged commit 668710a into master Jun 28, 2019
@toolness toolness deleted the yarn branch June 28, 2019 13:55
toolness added a commit that referenced this pull request Jun 28, 2019
I discovered while working on #706 that the `selector` option I passed to react-testing-library's API's (e.g. `getByLabelText()`) wasn't actually serving as a filter on the query the way I thought it was, so this fixes that.
toolness added a commit that referenced this pull request Jul 10, 2019
Aside from somehow being orders of magnitude faster than npm, it also makes it easier to install into arbitrary directories, which is especially useful for potentially getting around a very strange docker bug on Johanna's system.

## Notes

* Upgraded apollo to get around apollographql/apollo-tooling#1329.

* I tried using a tool to convert our `package-lock.json` to a `yarn.lock` but it didn't work, so I just built our `yarn.lock` directly from the `package.json`.  This has resulted in some intermediate dependencies being different, which ultimately required me to upgrade a few packages.

    * One such package was `@testing-library/react`, which uncovered #707 (which we will deal with separately).
toolness added a commit that referenced this pull request Jul 10, 2019
I discovered while working on #706 that the `selector` option I passed to react-testing-library's API's (e.g. `getByLabelText()`) wasn't actually serving as a filter on the query the way I thought it was, so this fixes that.
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.

None yet

1 participant