React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

• @vitejs/plugin-react uses Babel (or oxc when used in rolldown-vite) for Fast Refresh
• @vitejs/plugin-react-swc uses SWC for Fast Refresh

React Compiler

The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:

export default defineConfig([
  globalIgnores(['dist']),
  {
    files: ['**/*.{ts,tsx}'],
    extends: [
      // Other configs...

      // Remove tseslint.configs.recommended and replace with this
      tseslint.configs.recommendedTypeChecked,
      // Alternatively, use this for stricter rules
      tseslint.configs.strictTypeChecked,
      // Optionally, add this for stylistic rules
      tseslint.configs.stylisticTypeChecked,

      // Other configs...
    ],
    languageOptions: {
      parserOptions: {
        project: ['./tsconfig.node.json', './tsconfig.app.json'],
        tsconfigRootDir: import.meta.dirname,
      },
      // other options...
    },
  },
])

You can also install eslint-plugin-react-x and eslint-plugin-react-dom for React-specific lint rules:

// eslint.config.js
import reactX from 'eslint-plugin-react-x'
import reactDom from 'eslint-plugin-react-dom'

export default defineConfig([
  globalIgnores(['dist']),
  {
    files: ['**/*.{ts,tsx}'],
    extends: [
      // Other configs...
      // Enable lint rules for React
      reactX.configs['recommended-typescript'],
      // Enable lint rules for React DOM
      reactDom.configs.recommended,
    ],
    languageOptions: {
      parserOptions: {
        project: ['./tsconfig.node.json', './tsconfig.app.json'],
        tsconfigRootDir: import.meta.dirname,
      },
      // other options...
    },
  },
])

The Hack: A Visual and Narrative Sequence

The terminal interface isn't just a command-line simulator—it's a scripted, multi-stage hacking narrative designed to look like a blockbuster movie sequence. When the sequence executes, here is exactly what the user sees and experiences on the screen:

Phase 1: The Breach

• The Entry: The sequence begins with rapid, automated execution of a remote exploit script (exploit_cve_2024_0891.py).
• The Shell: The user sees the payload inject, bypass secondary firewalls, and drop them straight into a root bash shell.
• The Login Portal: A secure authentication server prompts for credentials (ADMIN:GHOST_PROTOCOL), elevating access to the highest possible clearance level (Level 5 / ULTRA).

Phase 2: The Vault and The Discovery

• Browsing Secrets: The hacker issues a simple ls -la command to view the contents of a highly classified vault. Directory names like TREADSTONE, BLACKBRIAR, and OUTCOME flash on the screen.
• File Interrogation: The hacker extracts four top-secret databases one by one. As each file is decrypted and accessed, a floating tactical window pops up directly over the terminal.
• The Exfiltration (Visual Stack): Since the hacker doesn't close them, these windows stack up on the screen, creating a cluttered, chaotic, "too much information at once" vibe.
• The Grand Theft: With the files exposed on screen, a massive multi-file progress dialog takes over the center. It shows 4.5 GB of ultra-classified data steadily siphoning off to an anonymous exit node in real time. Once complete, it sweeps all the open windows off the screen like a master thief cleaning their tracks.

Phase 3: The Danger sequence (Caught in the Act)

• The Alarm: Suddenly, the screen flashes deep red. A massive [!] HOSTILE INTRUSION DETECTED [!] banner drops from the top. The entire UI goes into full "Panic Mode," vibrating and tearing with digital artifacts and scanlines.
• Counter-Hack: The system is tracing the hacker! A Network Threat Map drops down—a live wireframe graph showing three international intelligence agencies (NSA, GCHQ, CIA) triangulating the hacker's IP address.
• Packet Intercepts: Automated counter-measure code begins flashing across the screen in red popup windows—raw packet dumps and automated nuclear failsafe codes executing in real-time, appearing and auto-closing in a frantic rush.

Phase 4: Evasion and Ghosting

• The Escape: As the global intelligence agencies close in and the trace threatens to reach 100%, the hacker executes a series of desperate countermeasures: spoofing MAC addresses, rebuilding Tor circuits, and injecting 10-gigabit noise packets into the trackers.
• The Decoy Swarm: Just as they are cornered, the hacker launches 200 decoy sessions worldwide. A massive grid of progress bars fills the screen as the trackers are overwhelmed and blinded by the noise.
• Disappearance: The trace signals degrades to 0.3% accuracy. The connections drop. The agencies lose the lock. The red flashing stops, gracefully fading back into the safety of the green ambient glow. The terminal spits out a final STATUS: SECURE, leaving the hacker entirely vanished—having stolen the most guarded secrets on Earth without a trace.