Unverified Commit 804dc6bd authored by Đorđe Spasić's avatar Đorđe Spasić Committed by GitHub

fix: eslint no-script-component-in-head error url (#40422)



## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [x] Make sure the linting passes by running `pnpm lint`
- [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
Co-authored-by: 's avatarJJ Kasper <22380829+ijjk@users.noreply.github.com>
parent 73557570
const url =
'https://nextjs.org/docs/messages/no-script-component-in-head-component'
const url = 'https://nextjs.org/docs/messages/no-script-component-in-head'
module.exports = {
meta: {
......
......@@ -44,7 +44,7 @@ ruleTester.run('no-script-in-head', rule, {
errors: [
{
message:
'`next/script` should not be used in `next/head` component. Move `<Script />` outside of `<Head>` instead. See: https://nextjs.org/docs/messages/no-script-component-in-head-component',
'`next/script` should not be used in `next/head` component. Move `<Script />` outside of `<Head>` instead. See: https://nextjs.org/docs/messages/no-script-component-in-head',
},
],
},
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment