From 817203d03ba1bd9194841851774b1768572df6ee Mon Sep 17 00:00:00 2001 From: Masen Furer <m_github@0x26.net> Date: Thu, 22 Apr 2021 11:46:25 -0700 Subject: [PATCH] Update using-the-public-folder.md Update link to `pace.js` docs --- 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 71266db6f..23b9c34ac 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/docs/) outside of the bundled code. - Some libraries may be incompatible with webpack and you have no other option but to include it as a `<script>` tag. Note that if you add a `<script>` that declares global variables, you should read the topic [Using Global Variables](using-global-variables.md) in the next section which explains how to reference them. -- GitLab