script/no-restricted-globals

Disallow references to runtime-environment globals that must go through a typed wrapper

Bad · Good

Default severity: error
Presets: none
Automatic fix: None; review the suggested change
Applies to: JS/TS scripts in Vue SFCs; examples show the relevant Options API or script setup form
Options: See typed options and defaults.

Configuration (Vite+)

import { defineConfig } from "@vizejs/vite-plugin/vite-plus";

export default defineConfig({
  lint: {
    vize: {
      "preset": "incremental",
      "rules": {
        "script/no-restricted-globals": "error"
      }
    },
  },
});

vp run lint

Bad

The example reads the default restricted globals process, localStorage, and sessionStorage directly, bypassing the project’s explicit config and storage helpers.

<script setup lang="ts">
const flag = process.env.FEATURE_FLAG
const token = localStorage.getItem('auth.token')
sessionStorage.setItem('view.scroll', String(window.scrollY))
</script>

Good

useFeatureFlag, authStorage.read, and viewStorage.write remove those direct restricted-global references. The remaining window.scrollY is not a default restriction of this rule; SSR safety is a separate concern.

<script setup lang="ts">
// Use a typed config helper that distinguishes server vs. client.
const flag = useFeatureFlag('FEATURE_FLAG')

// Use a typed wrapper that scopes keys and handles SSR / disabled storage.
const token = authStorage.read('auth.token')
viewStorage.write('view.scroll', String(window.scrollY))
</script>

Good avoids this rule's finding under the configuration above; other rules may still report diagnostics.

Implementation · All rules