Broken anchors: page not scroll to the right section

[JEricaM]

Broken anchors: page not scroll to the right section

[fuxin967]

Hi @AnthonyTsu1984 , thank you for your quick reply. Actually I tried to create a brand new project using scaffold command
npx create-docusaurus@latest my-website classic --typescript
which has exact the same dependencies as you pointed out, and it does not work also.
Another tried is creating a repro with https://new.docusaurus.io/, also does not work.

And the issue is not about broken anchor warnings, it's about clicking a url with an anchor and it does not scroll to the right position

[JEricaM]

@slorber thank you so much for the answer!! solved my problem :D

[AnthonyTsu1984]

Hi, probably the same issue here.
I have a Chinese site where I add anchor id manually as follows:

But I don't know why such titles carry no anchor styles, and I assume that makes all anchors broken.

[JEricaM]

yes I think is the same error :(

[AnthonyTsu1984]

I have checked the differences between the dependencies of a fresh-install site and my site, and it turns out that it's the fault of the dependencies. Clean your dependencies and remove conflicting and unnecessary dependencies. Everything will go smoothly then.

[fuxin967]

Also have the same issue

[AnthonyTsu1984]

Also have the same issue

Try to clean the dependencies as I do. The update command that Docusaurus provides does not cover everything.

Check your package.json and make sure that you have these dependencies with the correct versions.

After cleaning my dependencies, the broken anchor warnings are gone forever.

[slorber]

Hey

The problem on this url is a hosting problem.
https://docs.avacysolution.com/docs/avacy-saas/cookie-policy#aggiornamenti-ai-termini-della-cookie-policy

This URL is not supposed to serve build/index.html, but it actually does.

If you throttle your network (using Chrome devtools) or plainly disable JS, you will see that your web server serves your index/homepage instead of the actual page it's supposed to serve. The UI gets "fixed" later because React takes over and re-renders it with the content you expect. But the problem remains: you don't serve the correct page.

It is your responsibility to configure your custom hosting solution to serve a static deployment properly. I'd recommend using Vercel or Netlify to make this a no-brainer in case you don't know how to fix the problem on your current host.

---

Regarding problems encountered by others, they are likely different problems. Please create repros using https://docusaurus.new/stackblitz and we'll take a look.