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

standardize on using yarn and yarn lockfile #277

Closed
4 tasks
shiftkey opened this issue Jan 30, 2019 · 2 comments · Fixed by #493
Closed
4 tasks

standardize on using yarn and yarn lockfile #277

shiftkey opened this issue Jan 30, 2019 · 2 comments · Fixed by #493

Comments

@shiftkey
Copy link
Member

The other projects in this organization use yarn, and this is currently the only exception:

  • import a vendored yarn and add the related .yarnrc config
  • regenerate the lockfile
  • remove any package.json scripts that might use npm directly
  • test a release using yarn and update documentation
@j-f1
Copy link

j-f1 commented Jan 30, 2019

What do you think about making a desktop/scripts repo that has the vendored yarn (plus other common deps like TS), and include it as a submodule in all repos?

@shiftkey
Copy link
Member Author

It's something that interests me, but for the moment I'd like to follow the rule of 3 to identify what's actually needed in this hypothetical situation.

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 a pull request may close this issue.

2 participants