GET layoutComponents return 404

[mrdrivingduck]

Recently, I have upgraded my project from 2.0.0-beta-48 to 53. When I tried to preview my website locally, I got:

GET http://localhost:8080/${project_name}/home/${user_name}/${project_name}/docs/.vuepress/.temp/internal/layoutComponents net::ERR_ABORTED 404 (Not Found)

Seems it is a invalid path.

But when I comment the docSearch plugin in my config, the error no longer exists:

  plugins: [
    // docsearchPlugin({
    //   appId: "xxx",
    //   apiKey: "xxx",
    //   indexName: "xxx",
    //   locales: {
    //     "/": {
    //       placeholder: "Search Documentation",
    //     },
    //   },
    // }),
  ]

Any solutions by the maintainers? Thanks.

[Mister-Hope]

Check whether you are using same version of vuepress and all it's subpackages and official plugins.

[mrdrivingduck]

Why do you express an attitude of sigh (if I am not understand mistakenly by the word sign)?

As far as I can see:

1. I have done what you have told me to do, trying best to prove the problem is not on my side
2. Half a month later from my question, more and more people are meeting up with similar problem, and turns out it is a problem of npm, the so called invalid repro is not something I can control
3. the purpose I asked the question is to make sure the problem has been solved, is it a rude enough question to make you sigh?

[Mister-Hope]

1. I am a Collaborator of the repo, and I have no rights to publish package, so I can not contact npm support. Meteorlxy should be in charged of those things.
2. This is an open source project and I have study and work to do, also I gets 50+ emails and 30+ github notification per day, so I don't think I shall ensure I reply all of them. Issue is a place I will check in periods, but not dicussion, as discussion probably means that this is a help or other thing personal
3. For the late reply, I believed I ahead to stackbliuz to check what you are reporting (I have memory on this, but there must be something which stops me from finish the reproduction and reply you like study, I do be busy)
4. I still think that I provide explaination and solution to this, as I pointed out in the second reply "Then you should provide a repro, also make sure you are no using beta.50-pre.x" and I still get a repo with beta.50-pre.x. It's not about your attitude, it's just me a poor postgraduate student majored in theoretical physics busy at study all day, and still find a notification which ask me to have a little more explain politely.

Does yarn has a similar problem?

Yes, but I absolutely do not want to answer question like this, because it's definitely out of scope for me to explain how node package version works and what's a package manager and "will I get different pacakge version with differernt pacakge manager". The problem is about the first one, and definitely nothing related to 2 so the 3 is "NO".

If my reply confuse you, I would like to apologize, but I am sure you know that a lot of open source repo maintainers won't check discussion (e.g: vuejs/core), so at least you should somehow agree that it's not a fault for a maintainer to leave a discussion here just because he forgot it.

[meteorlxy]

I'm still talking with npm support about those fxxking pre-x versions. 😃

[mrdrivingduck]

@Mister-Hope I'm not complaining about the late reply from you. I pretty understand most open source project maintainers work as part-time. Also, I'm not expecting any reply from you, which is the reason I asked the question in discussion part. I just want to try my luck if anyone can help, because my work is mostly about C programming, so I'm not familiar with front end techs.

I am just confused about the word sign because it seems that you are inpatient with this kind of question. It is okay if you ignore my question. And also, thanks for your detailed explanation of my question, it really helps. Wish you good to your study.

[Mister-Hope]

I'm still talking with npm support about those fxxking pre-x versions. 😃

So any actual progress?