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

Get rid of yarn v1 for good! #1202

Open
landsman opened this issue Aug 3, 2023 · 5 comments
Open

Get rid of yarn v1 for good! #1202

landsman opened this issue Aug 3, 2023 · 5 comments

Comments

@landsman
Copy link

landsman commented Aug 3, 2023

Guys, I really hate this day-to-day scenario when Google returns links to https://classic.yarnpkg.com/* as the first result. It's so annoying!

Could you please disable indexing for this website and, for God's sake, get rid of it permanently? 🙏

Please promote the latest version and place the history as a secondary option, somehow hidden below, like every other tool and service.

Is there any way I can help? 🙏


For context to others:

  • The latest version is now: v3.6.1
  • This repository maintains a website for v1.x

Related: yarnpkg/yarn#8973

@landsman
Copy link
Author

landsman commented Aug 3, 2023

A few examples:

Screenshot 2023-08-03 at 15 38 58

Screenshot 2023-08-03 at 15 39 34

Screenshot 2023-08-03 at 15 39 54

It's time...

@arcanis
Copy link
Member

arcanis commented Aug 3, 2023

Yes, I think removing the index is fine. We're actually wrapping up the new website, so we can do that once it's deployed (a couple of weeks).

@tspearconquest
Copy link

I'd also like to take a second to point out that the node docker image still pulls yarn 1.22.19. If anyone here has a connection with the team who manages the docker library where that image is built from, can you please ask them to update the images to use a supported yarn version?

@Daniel15
Copy link
Member

Daniel15 commented Aug 10, 2023

Doesn't this mean that the old site has better SEO than the new site? 🤔

get rid of it permanently?

If we want to remove the old site, all the old URLs should 301 (permanent redirect) to the correct page on the new site, for all languages the old site supported, such that none of the URLs indexed in Google become 404 errors.

There's still a bunch of people using Yarn v1 though, so maybe we do still need the content. Perhaps it can be integrated into the new site (e.g. a version dropdown or something)?

I'd also like to take a second to point out that the node docker image still pulls yarn 1.22.19.

As far as I can remember, Yarn v2 and newer are not designed to be installed globally in the same way that Yarn v1 was, which is why the Docker image, Debian package, etc are all still using Yarn v1. You can still have Yarn v1 installed globally but use Yarn v2/v3/... on a per-project basis.

@landsman
Copy link
Author

landsman commented Aug 10, 2023

@Daniel15 the goal is to index only latest version. Then you can provide dropdown with redirect to archived website with no-index flag for robots.

all the old URLs should 301 (permanent redirect) to the correct page on the new site

yeah I would redirect all of them to latest website, index (where will be notice about archive) => Google will remove them from SERP as duplicate.

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

No branches or pull requests

4 participants