diff --git a/.eslintrc.json b/.eslintrc.json index b642bbc5c14..40029410cce 100644 --- a/.eslintrc.json +++ b/.eslintrc.json @@ -4,7 +4,8 @@ "browser": true, "commonjs": true, "node": true, - "es6": true + "es6": true, + "jest": true }, "parserOptions": { "ecmaVersion": 2018 diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 8153cffe3e2..0f391681bef 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -32,7 +32,7 @@ labels: 'issue: bug report, needs triage' * yarn.lock Then you need to decide which package manager you prefer to use. - We support both npm (https://npmjs.com) and yarn (http://yarnpkg.com/). + We support both npm (https://npmjs.com) and yarn (https://yarnpkg.com/). However, **they can't be used together in one project** so you need to pick one. If you decided to use npm, run this in your project directory: diff --git a/.github/workflows/integration.yml b/.github/workflows/integration.yml new file mode 100644 index 00000000000..1249f20532f --- /dev/null +++ b/.github/workflows/integration.yml @@ -0,0 +1,36 @@ +name: Integration Tests + +on: + push: + branches: + - master + pull_request: + branches: + - master + +jobs: + job: + runs-on: ${{ matrix.os }} + strategy: + matrix: + os: ['ubuntu-latest', 'macos-latest', 'windows-latest'] + node: ['10', '12', '14'] + steps: + - uses: actions/checkout@v2 + - name: Setup node + uses: actions/setup-node@v1 + with: + node-version: ${{ matrix.node }} + - name: Cache dependencies + id: cache + uses: actions/cache@v2 + with: + path: | + node_modules + */*/node_modules + key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock', './yarn.lock') }} + - name: Install packages + if: steps.cache.outputs.cache-hit != 'true' + run: yarn --frozen-lockfile --prefer-offline + - name: Run integration tests + run: yarn test:integration diff --git a/CHANGELOG-0.x.md b/CHANGELOG-0.x.md index 357f8231ee5..ea3fa82446a 100644 --- a/CHANGELOG-0.x.md +++ b/CHANGELOG-0.x.md @@ -156,7 +156,7 @@ npm install -g create-react-app@1.3.0 If you are using Yarn, and you have created at least one app previously, Create React App now works offline. - Yarn offline installation demo + Yarn offline installation demo #### :bug: Bug Fix @@ -515,7 +515,7 @@ Inside any created project that has not been ejected, run: npm install --save-dev --save-exact react-scripts@0.9.0 ``` -Then, run your tests. If you are affected by breaking changes from Jest 18, consult [blog post](https://facebook.github.io/jest/blog/2016/12/15/2016-in-jest.html), [changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md#jest-1800), and [documentation](http://facebook.github.io/jest/docs/getting-started.html). You might need to update any snapshots since their format might have changed. +Then, run your tests. If you are affected by breaking changes from Jest 18, consult [blog post](https://facebook.github.io/jest/blog/2016/12/15/2016-in-jest.html), [changelog](https://github.com/facebook/jest/blob/master/CHANGELOG.md#jest-1800), and [documentation](https://facebook.github.io/jest/docs/getting-started.html). You might need to update any snapshots since their format might have changed. If you relied on the browser not starting in non-interactive terminals, you now need to explicitly specify `BROWSER=none` as an environment variable to disable it. @@ -993,7 +993,7 @@ Thanks to [@fson](https://github.com/fson) for cutting this release. ### Build Dependency (`react-scripts`) -- Updates Jest to [version 16.0](http://facebook.github.io/jest/blog/2016/10/03/jest-16.html), with an upgraded CLI, improved snapshot testing, new matchers and more. ([@chase](https://github.com/chase) in [#858](https://github.com/facebook/create-react-app/pull/858)) +- Updates Jest to [version 16.0](https://facebook.github.io/jest/blog/2016/10/03/jest-16.html), with an upgraded CLI, improved snapshot testing, new matchers and more. ([@chase](https://github.com/chase) in [#858](https://github.com/facebook/create-react-app/pull/858)) - Test setup file `src/setupTests.js` is now called after test framework initialization to support loading custom matchers. ([@just-boris](https://github.com/just-boris) in [#846](https://github.com/facebook/create-react-app/pull/846)) - Build command shows better instructions for deploying the app to GitHub Pages ([@Janpot](https://github.com/Janpot) in [#841](https://github.com/facebook/create-react-app/pull/841)) - Build command now generates an asset manifest with mappings from each filename to its final output filename. ([@lukyth](https://github.com/lukyth) in [#891](https://github.com/facebook/create-react-app/pull/891)) @@ -1394,7 +1394,7 @@ Newly created projects will use `0.2.1` automatically. You **don’t** need to u - You can now enable deployment to GitHub Pages by adding `homepage` field to `package.json` ([@dhruska](https://github.com/dhruska) in [#94](https://github.com/facebook/create-react-app/pull/94)) - Development server now runs on `0.0.0.0` and works with VirtualBox ([@JWo1F](https://github.com/JWo1F) in [#128](https://github.com/facebook/create-react-app/pull/128)) -- Cloud9 and Nitrous online IDEs are now supported ([@gaearon](http://github.com/gaearon) in [2fe84e](https://github.com/facebook/create-react-app/commit/2fe84ecded55f1d5258d91f9c2c07698ae0d2fb4)) +- Cloud9 and Nitrous online IDEs are now supported ([@gaearon](https://github.com/gaearon) in [2fe84e](https://github.com/facebook/create-react-app/commit/2fe84ecded55f1d5258d91f9c2c07698ae0d2fb4)) - When `3000` port is taken, we offer to use another port ([@chocnut](https://github.com/chocnut) in [#101](https://github.com/facebook/create-react-app/pull/101), [2edf21](https://github.com/facebook/create-react-app/commit/2edf2180f2aa6bf647807d0b1fcd95f4cfe4a558)) - You can now `import` CSS files from npm modules ([@glennreyes](https://github.com/glennreyes) in [#105](https://github.com/facebook/create-react-app/pull/105), [@breaddevil](https://github.com/breaddevil) in [#178](https://github.com/facebook/create-react-app/pull/178)) - `fetch` and `Promise` polyfills are now always included ([@gaearon](https://github.com/gaearon) in [#235](https://github.com/facebook/create-react-app/pull/235)) diff --git a/CHANGELOG-1.x.md b/CHANGELOG-1.x.md index d8b8ee9cb90..cc629cf5f95 100644 --- a/CHANGELOG-1.x.md +++ b/CHANGELOG-1.x.md @@ -1547,7 +1547,7 @@ You can automatically convert your project to fix them by running the [correspon #### How do I make my tests work with Jest 20? -Please refer to the [Jest 19](https://facebook.github.io/jest/blog/2017/02/21/jest-19-immersive-watch-mode-test-platform-improvements.html#breaking-changes) and [Jest 20](http://facebook.github.io/jest/blog/2017/05/06/jest-20-delightful-testing-multi-project-runner.html#breaking-changes) breaking changes for migration instructions. +Please refer to the [Jest 19](https://facebook.github.io/jest/blog/2017/02/21/jest-19-immersive-watch-mode-test-platform-improvements.html#breaking-changes) and [Jest 20](https://facebook.github.io/jest/blog/2017/05/06/jest-20-delightful-testing-multi-project-runner.html#breaking-changes) breaking changes for migration instructions. If you use snapshots, you will likely need to update them once because of the change in format. diff --git a/CHANGELOG.md b/CHANGELOG.md index 472542ee341..8d32f878ccc 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,40 @@ +## 4.0.3 (2021-02-22) + +v4.0.3 is a maintenance release that includes minor bug fixes and dependency updates. + +#### :bug: Bug Fix + +- `react-scripts` + - [#10590](https://github.com/facebook/create-react-app/pull/10590) Upgrade eslint-webpack-plugin to fix opt-out flag ([@mrmckeb](https://github.com/mrmckeb)) + +#### :house: Internal + +- `react-dev-utils` + - [#10412](https://github.com/facebook/create-react-app/pull/10412) update immer to 8.0.1 to address vulnerability ([@wclem4](https://github.com/wclem4)) +- `create-react-app` + - [#10384](https://github.com/facebook/create-react-app/pull/10384) tests: update test case to match the description ([@jamesgeorge007](https://github.com/jamesgeorge007)) + +#### Committers: 4 + +- Brody McKee ([@mrmckeb](https://github.com/mrmckeb)) +- Dion Woolley ([@Awarua-](https://github.com/Awarua-)) +- James George ([@jamesgeorge007](https://github.com/jamesgeorge007)) +- Walker Clem ([@wclem4](https://github.com/wclem4)) + +# Migrating from 4.0.2 to 4.0.3 + +Inside any created project that has not been ejected, run: + +```bash +npm install --save --save-exact react-scripts@4.0.3 +``` + +or + +``` +yarn add --exact react-scripts@4.0.3 +``` + ## 4.0.2 (2021-02-03) v4.0.2 is a maintenance release that includes minor bug fixes and documentation updates. diff --git a/docusaurus/docs/adding-a-sass-stylesheet.md b/docusaurus/docs/adding-a-sass-stylesheet.md index 1ba76380e6a..fb1a23af00b 100644 --- a/docusaurus/docs/adding-a-sass-stylesheet.md +++ b/docusaurus/docs/adding-a-sass-stylesheet.md @@ -10,42 +10,36 @@ Generally, we recommend that you don’t reuse the same CSS classes across diffe Following this rule often makes CSS preprocessors less useful, as features like mixins and nesting are replaced by component composition. You can, however, integrate a CSS preprocessor if you find it valuable. -To use Sass, first install `node-sass`: +To use Sass, first install `sass`: ```sh -$ npm install node-sass --save -$ # or -$ yarn add node-sass +$ npm install sass +# or +$ yarn add sass ``` Now you can rename `src/App.css` to `src/App.scss` and update `src/App.js` to import `src/App.scss`. This file and any other file will be automatically compiled if imported with the extension `.scss` or `.sass`. -To share variables between Sass files, you can use Sass imports. For example, `src/App.scss` and other component style files could include `@import "./shared.scss";` with variable definitions. +To share variables between Sass files, you can use Sass's [`@use` rule](https://sass-lang.com/documentation/at-rules/use). For example, `src/App.scss` and other component style files could include `@use "./shared.scss";` with variable definitions. This will allow you to do imports like ```scss -@import 'styles/_colors.scss'; // assuming a styles directory under src/ -@import '~nprogress/nprogress'; // importing a css file from the nprogress node module +@use 'styles/_colors.scss'; // assuming a styles directory under src/ +@use '~nprogress/nprogress'; // loading a css file from the nprogress node module ``` -> **Note:** You must prefix imports from `node_modules` with `~` as displayed above. +> **Note:** You can prefix paths with `~`, as displayed above, to resolve modules from `node_modules`. -`node-sass` also supports the `SASS_PATH` variable. +`sass` also supports the `SASS_PATH` variable. -To use imports relative to a path you specify, and from `node_modules` without adding the `~` prefix, you can add a [`.env` file](https://github.com/facebook/create-react-app/blob/master/docusaurus/docs/adding-custom-environment-variables.md#adding-development-environment-variables-in-env) at the project root with the variable `SASS_PATH=node_modules:src`. To specify more directories you can add them to `SASS_PATH` separated by a `:` like `path1:path2:path3`. +To use imports relative to a path you specify, you can add a [`.env` file](https://github.com/facebook/create-react-app/blob/master/docusaurus/docs/adding-custom-environment-variables.md#adding-development-environment-variables-in-env) at the project root with the path specified in the `SASS_PATH` environment variable. To specify more directories you can add them to `SASS_PATH` separated by a `:` like `path1:path2:path3`. -If you set `SASS_PATH=node_modules:src`, this will allow you to do imports like -```scss -@import 'styles/colors'; // assuming a styles directory under src/, where _colors.scss partial file exists. -@import 'nprogress/nprogress'; // importing a css file from the nprogress node module -``` - -> **Note:** For windows operating system, use below syntax +> **Note:** For the Windows operating system, separate your paths by semicolons. > > ``` -> SASS_PATH=./node_modules;./src +> SASS_PATH=path1;path2;path3 > ``` > **Tip:** You can opt into using this feature with [CSS modules](adding-a-css-modules-stylesheet.md) too! @@ -61,3 +55,14 @@ If you set `SASS_PATH=node_modules:src`, this will allow you to do imports like > module.file_ext=.sass > module.file_ext=.scss > ``` + +> **Note:** LibSass and the packages built on top of it, including Node Sass, are [deprecated](https://sass-lang.com/blog/libsass-is-deprecated). +> If you're a user of Node Sass, you can migrate to Dart Sass by replacing `node-sass` in your `package.json` file with `sass` or by running the following commands: +> +> ```sh +> $ npm uninstall node-sass +> $ npm install sass +> # or +> $ yarn remove node-sass +> $ yarn add sass +> ``` \ No newline at end of file diff --git a/docusaurus/docs/adding-bootstrap.md b/docusaurus/docs/adding-bootstrap.md index 1bbffda0854..7ca91c07fd2 100644 --- a/docusaurus/docs/adding-bootstrap.md +++ b/docusaurus/docs/adding-bootstrap.md @@ -8,7 +8,7 @@ While you don’t have to use any specific library to integrate Bootstrap with R Each project's respective documentation site has detailed instructions for installing and using them. Both depend on the Bootstrap css file so install that as well: ```sh -npm install --save bootstrap +npm install bootstrap ``` Alternatively you may use `yarn`: @@ -33,19 +33,19 @@ Sometimes you might need to tweak the visual styles of Bootstrap (or equivalent As of `react-scripts@2.0.0` you can import `.scss` files. This makes it possible to use a package's built-in Sass variables for global style preferences. -To enable `scss` in Create React App you will need to install `node-sass`. +To enable `scss` in Create React App you will need to install `sass`. ```sh -npm install --save node-sass +npm install sass ``` Alternatively you may use `yarn`: ```sh -yarn add node-sass +yarn add sass ``` -To customize Bootstrap, create a file called `src/custom.scss` (or similar) and import the Bootstrap source stylesheet. Add any overrides _before_ the imported file(s). You can reference [Bootstrap's documentation](https://getbootstrap.com/docs/4.1/getting-started/theming/#css-variables) for the names of the available variables. +To customize Bootstrap, create a file called `src/custom.scss` (or similar) and import the Bootstrap source stylesheet. Add any overrides _before_ the imported file(s). You can reference [Bootstrap's documentation](https://getbootstrap.com/docs/4.6/getting-started/theming/#variable-defaults) for the names of the available variables. ```scss // Override default variables before the import @@ -55,7 +55,7 @@ $body-bg: #000; @import '~bootstrap/scss/bootstrap.scss'; ``` -> **Note:** You must prefix imports from `node_modules` with `~` as displayed above. +> **Note:** You can prefix paths with `~`, as displayed above, to resolve modules from `node_modules`. Finally, import the newly created `.scss` file instead of the default Bootstrap `.css` in the beginning of your `src/index.js` file, for example: diff --git a/docusaurus/docs/adding-css-reset.md b/docusaurus/docs/adding-css-reset.md index c08567124af..d57a1e3803c 100644 --- a/docusaurus/docs/adding-css-reset.md +++ b/docusaurus/docs/adding-css-reset.md @@ -66,7 +66,7 @@ Browser support is dictated by what normalize.css [supports]. As of this writing - iOS Safari (last 2) - Internet Explorer 9+ -[browserslist]: http://browserl.ist/ +[browserslist]: https://browserl.ist/ [css reset]: https://cssreset.com/what-is-a-css-reset/ [normalize.css]: https://github.com/csstools/normalize.css [supports]: https://github.com/csstools/normalize.css#browser-support diff --git a/docusaurus/docs/advanced-configuration.md b/docusaurus/docs/advanced-configuration.md index 336d28cb2a2..7cc9f14f888 100644 --- a/docusaurus/docs/advanced-configuration.md +++ b/docusaurus/docs/advanced-configuration.md @@ -24,7 +24,7 @@ You can adjust various development and production settings by setting environmen | CHOKIDAR_USEPOLLING | ✅ Used | 🚫 Ignored | When set to `true`, the watcher runs in polling mode, as necessary inside a VM. Use this option if `npm start` isn't detecting changes. | | GENERATE_SOURCEMAP | 🚫 Ignored | ✅ Used | When set to `false`, source maps are not generated for a production build. This solves out of memory (OOM) issues on some smaller machines. | | INLINE_RUNTIME_CHUNK | 🚫 Ignored | ✅ Used | By default, Create React App will embed the runtime script into `index.html` during the production build. When set to `false`, the script will not be embedded and will be imported as usual. This is normally required when dealing with CSP. | -| IMAGE_INLINE_SIZE_LIMIT | 🚫 Ignored | ✅ Used | By default, images smaller than 10,000 bytes are encoded as a data URI in base64 and inlined in the CSS or JS build artifact. Set this to control the size limit in bytes. Setting it to 0 will disable the inlining of images. | +| IMAGE_INLINE_SIZE_LIMIT | ✅ Used | ✅ Used | By default, images smaller than 10,000 bytes are encoded as a data URI in base64 and inlined in the CSS or JS build artifact. Set this to control the size limit in bytes. Setting it to `0` will disable the inlining of images. | | FAST_REFRESH | ✅ Used | 🚫 Ignored | When set to `false`, disables experimental support for Fast Refresh to allow you to tweak your components in real time without reloading the page. | | TSC_COMPILE_ON_ERROR | ✅ Used | ✅ Used | When set to `true`, you can run and properly build TypeScript projects even if there are TypeScript type check errors. These errors are printed as warnings in the terminal and/or browser console. | | ESLINT_NO_DEV_ERRORS | ✅ Used | 🚫 Ignored | When set to `true`, ESLint errors are converted to warnings during development. As a result, ESLint output will no longer appear in the error overlay. | diff --git a/docusaurus/docs/code-splitting.md b/docusaurus/docs/code-splitting.md index 2fabb6b40c0..9a31009fded 100644 --- a/docusaurus/docs/code-splitting.md +++ b/docusaurus/docs/code-splitting.md @@ -5,7 +5,7 @@ title: Code Splitting Instead of downloading the entire app before users can use it, code splitting allows you to split your code into small chunks which you can then load on demand. -This project setup supports code splitting via [dynamic `import()`](http://2ality.com/2017/01/import-operator.html#loading-code-on-demand). Its [proposal](https://github.com/tc39/proposal-dynamic-import) is in stage 4. The `import()` function-like form takes the module name as an argument and returns a [`Promise`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) which always resolves to the namespace object of the module. +This project setup supports code splitting via [dynamic `import()`](https://2ality.com/2017/01/import-operator.html#loading-code-on-demand). Its [proposal](https://github.com/tc39/proposal-dynamic-import) is in stage 4. The `import()` function-like form takes the module name as an argument and returns a [`Promise`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) which always resolves to the namespace object of the module. Here is an example: diff --git a/docusaurus/docs/deployment.md b/docusaurus/docs/deployment.md index 201ce21cd76..478c0b9e653 100644 --- a/docusaurus/docs/deployment.md +++ b/docusaurus/docs/deployment.md @@ -161,7 +161,7 @@ You can specify other environments in the same way. Variables in `.env.production` will be used as fallback because `NODE_ENV` will always be set to `production` for a build. -## [AWS Amplify](http://console.amplify.aws) +## [AWS Amplify](https://console.amplify.aws) The AWS Amplify Console provides continuous deployment and hosting for modern web apps (single page apps and static site generators) with serverless backends. The Amplify Console offers globally available CDNs, custom domain setup, feature branch deployments, and password protection. diff --git a/docusaurus/docs/importing-a-component.md b/docusaurus/docs/importing-a-component.md index 2f4a4c56a69..7f23cb9c7d5 100644 --- a/docusaurus/docs/importing-a-component.md +++ b/docusaurus/docs/importing-a-component.md @@ -5,7 +5,7 @@ title: Importing a Component This project setup supports ES6 modules thanks to webpack. -While you can still use `require()` and `module.exports`, we encourage you to use [`import` and `export`](http://exploringjs.com/es6/ch_modules.html) instead. +While you can still use `require()` and `module.exports`, we encourage you to use [`import` and `export`](https://exploringjs.com/es6/ch_modules.html) instead. For example: @@ -47,7 +47,7 @@ Named exports are useful for utility modules that export several functions. A mo Learn more about ES6 modules: - [When to use the curly braces?](https://stackoverflow.com/questions/36795819/react-native-es-6-when-should-i-use-curly-braces-for-import/36796281#36796281) -- [Exploring ES6: Modules](http://exploringjs.com/es6/ch_modules.html) +- [Exploring ES6: Modules](https://exploringjs.com/es6/ch_modules.html) - [Understanding ES6: Modules](https://leanpub.com/understandinges6/read#leanpub-auto-encapsulating-code-with-modules) ## Absolute Imports diff --git a/docusaurus/docs/making-a-progressive-web-app.md b/docusaurus/docs/making-a-progressive-web-app.md index 649fb9cb320..fc8ba0a0da9 100644 --- a/docusaurus/docs/making-a-progressive-web-app.md +++ b/docusaurus/docs/making-a-progressive-web-app.md @@ -39,14 +39,14 @@ case. In addition to creating your local `src/service-worker.js` file, it needs to be registered before it will be used. In order to opt-in to the offline-first behavior, developers should look for the following in their -[`src/index.js`](https://github.com/facebook/create-react-app/blob/master/packages/cra-template/template/src/index.js) +[`src/index.js`](https://github.com/cra-template/pwa/blob/master/packages/cra-template-pwa/template/src/index.js) file: ```js // If you want your app to work offline and load faster, you can change // unregister() to register() below. Note this comes with some pitfalls. // Learn more about service workers: https://cra.link/PWA -serviceWorker.unregister(); +serviceWorkerRegistration.unregister(); ``` As the comment states, switching `serviceWorker.unregister()` to @@ -82,7 +82,7 @@ or unreliable network. Note: Resources that are not generated by `webpack`, such as static files that are copied over from your local -[`public/` directory](https://github.com/facebook/create-react-app/blob/master/packages/cra-template/template/public/) +[`public/` directory](https://github.com/cra-template/pwa/tree/master/packages/cra-template-pwa/template/public/) or third-party resources, will not be precached. You can optionally set up Workbox [routes](https://developers.google.com/web/tools/workbox/guides/route-requests) to apply the runtime caching strategy of your choice to those resources. @@ -128,7 +128,7 @@ following into account: fetched the latest updates that will be available the next time they load the page (showing a "New content is available once existing tabs are closed." message). Showing these messages is currently left as an exercise to the developer, but as a - starting point, you can make use of the logic included in [`src/serviceWorker.js`](https://github.com/facebook/create-react-app/blob/master/packages/cra-template/template/src/serviceWorker.js), which + starting point, you can make use of the logic included in [`src/serviceWorkerRegistration.js`](https://github.com/cra-template/pwa/blob/master/packages/cra-template-pwa/template/src/serviceWorkerRegistration.js), which demonstrates which service worker lifecycle events to listen for to detect each scenario, and which as a default, only logs appropriate messages to the JavaScript console. @@ -160,11 +160,11 @@ following into account: ## Progressive Web App Metadata The default configuration includes a web app manifest located at -[`public/manifest.json`](https://github.com/facebook/create-react-app/blob/master/packages/cra-template/template/public/manifest.json), that you can customize with +[`public/manifest.json`](https://github.com/cra-template/pwa/blob/master/packages/cra-template-pwa/template/public/manifest.json), that you can customize with details specific to your web application. When a user adds a web app to their homescreen using Chrome or Firefox on -Android, the metadata in [`manifest.json`](https://github.com/facebook/create-react-app/blob/master/packages/cra-template/template/public/manifest.json) determines what +Android, the metadata in [`manifest.json`](https://github.com/cra-template/pwa/blob/master/packages/cra-template-pwa/template/public/manifest.json) determines what icons, names, and branding colors to use when the web app is displayed. [The Web App Manifest guide](https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/) provides more context about what each field means, and how your customizations diff --git a/docusaurus/docs/using-the-public-folder.md b/docusaurus/docs/using-the-public-folder.md index 71266db6f81..a33c3a29ec8 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://github.com/CodeByZach/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 `