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.

Sign up for GitHub

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

Jump to bottom

README refers inconsistently to Yarn and NPM #1457

Closed
wincent opened this issue Jan 21, 2019 · 0 comments
Closed

README refers inconsistently to Yarn and NPM #1457

wincent opened this issue Jan 21, 2019 · 0 comments
Assignees
@wincent
Labels
comp: documentation Issues related to documentation in general, be clayui.com or other means... status: next-release Issues that will enter into the next release

Comments

@wincent
Copy link
Contributor

wincent commented Jan 21, 2019

The Clay README instructs people to install and use Yarn, and we ship with a yarn.lock, but we don't consistently use yarn in the commands that we show in the README; we should fix that for consistency.

I actually already submitted #1454 for this, so creating this issue retroactively to follow the convention.
@wincent wincent added the comp: documentation Issues related to documentation in general, be clayui.com or other means... label Jan 21, 2019
@wincent wincent self-assigned this Jan 21, 2019
matuzalemsteles added a commit that referenced this issue Jan 21, 2019
@matuzalemsteles
Merge pull request #1454 from wincent/yarn-consistency
1c6e4b6 
Fixes #1457 - Refer to Yarn consistently in Clay README
@matuzalemsteles matuzalemsteles added the status: next-release Issues that will enter into the next release label Jan 21, 2019
@wincent wincent closed this as completed Jan 23, 2019
@carloslancha carloslancha reopened this Jan 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wincent wincent

Labels
comp: documentation Issues related to documentation in general, be clayui.com or other means... status: next-release Issues that will enter into the next release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@wincent @carloslancha @matuzalemsteles