From 5885638dda8a41fd21d7c7ea6d073a2756c2d51f Mon Sep 17 00:00:00 2001 From: Dmitry Ivanov Date: Sun, 21 Mar 2021 15:01:05 +0300 Subject: [PATCH] Fixed broken link for the pace.js --- docusaurus/docs/using-the-public-folder.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docusaurus/docs/using-the-public-folder.md b/docusaurus/docs/using-the-public-folder.md index 71266db6f81..dd511a6200a 100644 --- a/docusaurus/docs/using-the-public-folder.md +++ b/docusaurus/docs/using-the-public-folder.md @@ -60,7 +60,7 @@ The `public` folder is useful as a workaround for a number of less common cases: - You need a file with a specific name in the build output, such as [`manifest.webmanifest`](https://developer.mozilla.org/en-US/docs/Web/Manifest). - You have thousands of images and need to dynamically reference their paths. -- You want to include a small script like [`pace.js`](https://github.hubspot.com/pace/docs/welcome/) outside of the bundled code. +- You want to include a small script like [`pace.js`](https://codebyzach.github.io/pace/) outside of the bundled code. - Some libraries may be incompatible with webpack and you have no other option but to include it as a `