Skip to content

no-top-level-browser-globals rule is flagging types as top level browser globals #1226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
machadinhos opened this issue May 17, 2025 · 0 comments · Fixed by #1227
Closed
2 tasks done

Comments

@machadinhos
Copy link

Before You File a Bug Report Please Confirm You Have Done The Following...

  • I have tried restarting my IDE and the issue persists.
  • I have updated to the latest version of the packages.

What version of ESLint are you using?

9.27.0

What version of eslint-plugin-svelte are you using?

3.8.0

What did you do?

<script lang="ts">
  let element: HTMLElement;
  let submitHandler: SubmitEvent = (): void => {};
</script>

<form onsubmit={submitHandler}></form>
<div bind:this={element}></div>

What did you expect to happen?

It shouldn't flag types as top level browser globals, because, from my understanding, the objective of this rule is to prevent calling browser specific APIs (e.g. localStorage) while in the server.

What actually happened?

The new no-top-level-browser-globals rule is flagging types as top level browser globals.

Link to GitHub Repo with Minimal Reproducible Example

N.A.

Additional comments

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant