feat(code-quality): add ESLint flat config with TypeScript + React hooks rules - #1

eslint.config.mjs (1)

48-63: 🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

Scope runtime globals by file set.

The unscoped languageOptions.globals block applies both browser and Node globals to every file. This weakens no-undef checks across browser, Node, and Deno code. The Deno block also declares no Deno global, so its current Deno.* usages can produce lint errors. Scope browser, Node, and Deno globals to their respective file sets.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@eslint.config.mjs` around lines 48 - 63, Scope each languageOptions.globals
configuration to its corresponding browser, Node, or Deno file pattern instead
of applying it globally. Update the Deno configuration block for
functions/**/*.ts to declare the Deno global, while preserving the existing
TypeScript rules and ensuring each runtime’s globals do not leak into other file
sets.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

eslint.config.mjs:90

• The config currently applies both globals.browser and globals.node to every file. This makes Node-only globals (e.g. Buffer, process, etc.) appear valid in browser (apps/web/src) and Deno (functions/) code, which reduces linting’s ability to catch environment-specific mistakes. Consider scoping globals by runtime (browser/Deno vs Node tooling/tests) instead of enabling both everywhere.

  // Node/browser globals
  {
    languageOptions: {
      globals: {
        ...globals.browser,
        ...globals.node,
      },
    },
  },