From 804dc6bd103dbb9867b82d40e033fb33500a45df Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C4=90or=C4=91e=20Spasi=C4=87?= <34274884+Djo1e@users.noreply.github.com> Date: Mon, 12 Sep 2022 18:15:33 +0200 Subject: [PATCH] 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: JJ Kasper <22380829+ijjk@users.noreply.github.com> --- .../lib/rules/no-script-component-in-head.js | 3 +-- .../eslint-plugin-next/no-script-component-in-head.test.ts | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/packages/eslint-plugin-next/lib/rules/no-script-component-in-head.js b/packages/eslint-plugin-next/lib/rules/no-script-component-in-head.js index 379ef8e2d98c..9e342e738f42 100644 --- a/packages/eslint-plugin-next/lib/rules/no-script-component-in-head.js +++ b/packages/eslint-plugin-next/lib/rules/no-script-component-in-head.js @@ -1,5 +1,4 @@ -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: { diff --git a/test/unit/eslint-plugin-next/no-script-component-in-head.test.ts b/test/unit/eslint-plugin-next/no-script-component-in-head.test.ts index a6882b12b961..c4ae01685660 100644 --- a/test/unit/eslint-plugin-next/no-script-component-in-head.test.ts +++ b/test/unit/eslint-plugin-next/no-script-component-in-head.test.ts @@ -44,7 +44,7 @@ ruleTester.run('no-script-in-head', rule, { errors: [ { message: - '`next/script` should not be used in `next/head` component. Move `