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

Yarn support #11

Open
lysyi3m opened this Issue Dec 13, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@lysyi3m
Owner

lysyi3m commented Dec 13, 2016

For projects with yarn add support for version-matching based on yarn.lock file instead of package.json-based matching.

@spajic

This comment has been minimized.

Show comment
Hide comment

spajic commented Feb 23, 2017

#22

@haukot

This comment has been minimized.

Show comment
Hide comment
@haukot

haukot Dec 2, 2017

@lysyi3m Hi! Thanks for this gem, it is a cool solution for checking that all javascript packages installed.

Although it really useful with npm, I don't fully understand the goal of support yarn here.
This gem looks like an analog of yarn check with different formatting. So in the first place users that have yarn don't really need this gem. And for support yarn in this gem needs just change output of yarn check with output like this gem.

So it really needs to support yarn? And if it needs(e.g. for back compatibility), what you think about just run yarn check without changing its output?
Because the output format may change, and not seems very valuable for the end user to spend time on support. But maybe I wrong here and just look from my side.

haukot commented Dec 2, 2017

@lysyi3m Hi! Thanks for this gem, it is a cool solution for checking that all javascript packages installed.

Although it really useful with npm, I don't fully understand the goal of support yarn here.
This gem looks like an analog of yarn check with different formatting. So in the first place users that have yarn don't really need this gem. And for support yarn in this gem needs just change output of yarn check with output like this gem.

So it really needs to support yarn? And if it needs(e.g. for back compatibility), what you think about just run yarn check without changing its output?
Because the output format may change, and not seems very valuable for the end user to spend time on support. But maybe I wrong here and just look from my side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment