-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add more Yarn installation info #11
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm unsure about this change, the point of using npx is to avoid installing install-peerdeps as it's something that you're only going to use once. I'm also not a fan of installing things globally as it's prone to break very easily.
I wonder if there's a way of doing with yarn the same thing that npx does (running a command without actually installing it)?
(I'm not familiar with yarn, I have to say)
I'd advocate adding it as one of many options. We're already showing a I agree that we shouldn't force a global install on users of the package - that's very naughty. But showing an optional quick/automated installation method using a global package - I can't see a fundamental problem with that. I'll take a look and see if there's also a npx-ish way of doing things with Yarn. |
Hmmm, interestingly, there's no direct equivalent of |
How about just using npx? From what I can get that npx does, I don't think that using yarn to install deps prevents us from using npx. From your link:
|
Back from lunch. Hallo! I agree with that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazeballs 🥇
Hurrah! |
Add a quick addition based upon installing this package on a real Yarn environment.