chore: do not run no-dupe-on-directives rule on Svelte 5 with runes

[baseballyama]

No description provided.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/eslint-plugin-svelte@1010

commit: 0c0198f

[ota-meshi]

Thank you for the PR.
But I still don't understand. Can you tell me why this change is necessary?

[baseballyama]

Because compiler itself throws error.

https://svelte.dev/playground/hello-world?version=5.17.4#H4sIAAAAAAAAE23OzQrCMBAE4FeJc1IISq-hFrz5DsZD2qy0sCalu_5R-u4SQU_eho8ZmBkpXAkOR2LO5pEnjmZNcVCKG1hcBiaBO83Q11h6BWC_q8M4buVOrMXaIPTPu5yUkgoc6r4yHQeRvUfw-OXWo_k8WNW7vmp8goXSU-F0utFyXt7Pta24qAAAAA==

[ota-meshi]

Thank you for the explanation.

But I don't think the compiler will report the duplicates 🤔

<svelte:options runes />
<button on:click={foo} on:click={foo}>Hello!</button>

https://svelte.dev/playground/ac1bc2094524431abc508168f35e9f29?version=5.17.4

[baseballyama]

Ohhhhhhh

Hum, But this will generate another warning, which the user will need to correct anyway.
But anyway, yet this rule was found to be legitimate.😇

Using on:click to listen to the click event is deprecated. Use the event attribute onclick instead
https://svelte.dev/e/event_directive_deprecated (event_directive_deprecated)

[baseballyama]

We need to run this rule even in Svelte5 with runes.