Download next.js/test/e2e/app-dir/app-config-crossorigin/next.config.js from Devendra174/react-code-dataset: direct link, hf CLI and curl.
- Browser
- Download file 695 Bytes
-
https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/test/e2e/app-dir/app-config-crossorigin/next.config.js
- Command line
-
hf download hf://datasets/Devendra174/react-code-dataset/next.js/test/e2e/app-dir/app-config-crossorigin/next.config.js
-
curl -L -o next.config.js https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/test/e2e/app-dir/app-config-crossorigin/next.config.js
695 Bytes
| module.exports = { | |
| /** | |
| * The "assetPrefix" here doesn't needs to be real as we doesn't load the page in the browser in this test, | |
| * we only care about if all assets prefixed with the "assetPrefix" are having correct "crossOrigin". | |
| */ | |
| assetPrefix: 'https://example.vercel.sh', | |
| /** | |
| * According to HTML5 Spec (https://html.spec.whatwg.org/multipage/urls-and-fetching.html#cors-settings-attributes), | |
| * crossorigin="" and crossorigin="anonymous" has the same effect. And ReactDOM's preload methods (preload, preconnect, etc.) | |
| * will prefer crossorigin="" to save bytes. | |
| * | |
| * So we use "use-credentials" here for easier testing. | |
| */ | |
| crossOrigin: 'use-credentials', | |
| } | |