rsnext/test/integration/app-document/next.config.js

module.exports = {
  crossOrigin: 'anonymous',
}
Fix #5674 Append crossOrigin on the client side too, add config option for crossOrigin (#5873) # Fixes https://github.com/zeit/next.js/issues/5674 This adds config option ```js // next.config.js module.exports = { crossOrigin: 'anonymous' } ``` This config option is defined in the webpack Define Plugin at build. `Head` and `NextScript` now use the config option, if it's not explicitly set on the element. This value is now passed to Webpack so it can add it to scripts that it loads. The value is now used in `PageLoader` (on the client) so it can add it to the scripts and links that it loads. Using `<Head crossOrigin>` or `<NextScript crossOrigin>` is now deprecated. 2018-12-13 01:05:21 +01:00			`module.exports = {`
Improve linting rules to catch more errors (#9374) * Update `packages/` * Update examples * Update tests * Update bench * Update top level files * Fix build * trigger 2019-11-11 04:24:53 +01:00			`crossOrigin: 'anonymous',`
Fix #5674 Append crossOrigin on the client side too, add config option for crossOrigin (#5873) # Fixes https://github.com/zeit/next.js/issues/5674 This adds config option ```js // next.config.js module.exports = { crossOrigin: 'anonymous' } ``` This config option is defined in the webpack Define Plugin at build. `Head` and `NextScript` now use the config option, if it's not explicitly set on the element. This value is now passed to Webpack so it can add it to scripts that it loads. The value is now used in `PageLoader` (on the client) so it can add it to the scripts and links that it loads. Using `<Head crossOrigin>` or `<NextScript crossOrigin>` is now deprecated. 2018-12-13 01:05:21 +01:00			`}`