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
[Feature] yarn global #821
Comments
The |
I don't know if this is set in stone yet, but I hope the team will reconsider. This is also a call to action for users: Upvote this if you feel the same way I do. |
For that you need to remove the folders manually. I don't recall where they are exactly depending on the system but they should be near your home folder.
You're right... Kinda. The thing is, adding commands just for the sake of "why not? We might lose users otherwise" just doesn't really make the cut for me. Such things have a cost not only in number of keystrokes, but also maintainance time. Working on Yarn is already fairly intense, I'm not sure it's necessarily a bad thing for the future of a community open source project to put maybe less weight into "growth hacking", and instead focus on making working on the project a joy rather than a burden. That being said, I'm fairly sure it would take me less than two hours to build a prototype And for all those that don't agree with my philosophy, fear not! Just imagine the 2.x doesn't exist and it'll be the exact same thing. Use the 1.x trunk, it'll always be exactly as good as it is now |
Thanks @arcanis! That's a [mostly] fair response
although I concede that if you were to look at 2.x as a brand new tool rather than an upgrade of an existing tool, then it would make perfect sense. I look at it as an upgrade, hence my divergent stance. All that aside, is it possible to get specific instructions on cleaning up global packages added to the migration guide? (IIRC I think I saw such a thing) Thanks again for all the hard work! |
ok so I understand that one-off scripts are quite doable with the speed yarn has and its cache. However does this not impact a lot cli tools out there that expect to be installed in some global folder? Not all tools are necessarily bound to projects with a package.json. For example I use 'live-server' all the time just to start up some random folder. Now it takes 3 seconds extra to start up with |
@joerideg I'm not sure what your point is, given that @arcanis has already stated:
So anyone can step in and build this feature and maintain it. For the set of people that currently work on v2 this feature is not a top priority at the moment. |
I ment to point out that, unless I am missing something, |
I agree strongly here. Being used to running Reducing the API surface and maintenance burden in v2 is probably necessary fo the longevity of the project, but it really does make the migration hard and confusing. A document detailing the thoughts behind the removal of the command and how new commands can replace old workflows would help a lot. Maybe even leaving the command |
Yep, that's very reasonable. I'll add a few missing "bridges" in the next release |
Thank you very much. I just want to add that in some cases you don't have a package.json when you wanted to run yarn dlx, and sometimes you need additional packages / eg. eslint @typescript-eslint/eslint-plugin to run your command. Would be nice if you cover these cases as well. |
There are many cases of CLI tools that you'd want available system-wide, it's very strange that this very commonly used and necessary feature has been just dropped without any replacement |
I haven't said there isn't. We simply don't see Yarn as a system package manager. It can be used to power a system package manager, but we don't really want to deal with the wiring needed to make that work, especially considering that we don't really use it ourselves (and I think that for something to be worthy of being in our repository, maintainers have to dogfood it). |
Not sure of the wording desired here but this confused me a bit when I migrated until I came across #821. I'm confident other people will be left confused as well. Wrote this based on what I read there in the aforementioned issue.
I would like to also point out, Running I could use |
I understand why the global install was removed, however I don't understand why yarn2 depends on yarn1 to work. What is wrong with installing yarn2 globally as you would every other package manager I can think of and use it only for dependency management within projects? |
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
So... This thread is about If you have specific ideas to improve the migration path (which is something I wholeheartly agree with), please open dedicated issues - or, even better, contribute a PR or two! Ask everyone who contributed so far, I think they'll tell you how reactive we are on PRs. I'll now close this since I don't plan to have any news about this in the immediate future. If you want |
Describe the user story
After the upgrade my global packages are not installable/removable/updateable any more.
Please bear with me, if i don't fully understand all concepts included. But i tried to google/search all issues/read the documentation and nowhere is a sentence about global binaries/packages.
Describe the solution you'd like
As an angular developer i am only able to update my build environment if '''yarn global''' is included.
Describe the drawbacks of your solution
As i said i am unsure if i fully understand all concepts and if '''yarn global''' has been left out intentionally.
Describe alternatives you've considered
After the upgrade my global packages are not installable/removable/updateable any more.
The text was updated successfully, but these errors were encountered: