AndyB

Just to add that now we're moving to 3.1 we've noticed a similar thing. We have three different docs sources in our site and linking from one to another throws...

> @andrewgbell is your link having `target: "_blank"` too? > > Because it wasn't mentioned in the original issue, but it's what matters to me here. > > If the...

This seems to have been resolved now by two things. 1, running the latest canary, 2, then adding a trailing slash after support below in docusaurus.config.js from ` to: "/support",...

Just to add we've recently rolled back from 3.1 to 3.0.1 for this exact same issue (we also have a large site). Normally would take approx 45 mins to build,...

> @andrewgbell it looks like the build-time increase is not related to the 3.1 upgrade, but rather the upgrade of a transitive dependency that has a perf regression. > >...

> > @andrewgbell it looks like the build-time increase is not related to the 3.1 upgrade, but rather the upgrade of a transitive dependency that has a perf regression. >...

> Still investigating your site @ravilach, but it looks like there are 2 problems: > > * the broken link checker now using node `new URL()` is much slower >...

> Still investigating your site @ravilach, but it looks like there are 2 problems: > > * the broken link checker now using node `new URL()` is much slower >...

> node_modules/@docusaurus/core/lib/server/brokenLinks.js @slorber Yes, that worked great! Replaced the file and ran it with: onBrokenLinks: "warn", onBrokenAnchors: "warn", onBrokenMarkdownLinks: "throw", And it built just as quick as earlier. Thanks for...

Hi @slorber , sorry yes. I'd been comparing 3.1 optimisations with 3.1 ignore broken links so hadn't spotted it. But looking again we get: 3.0 build time with handleBrokenLinks -...