windows-iso-downloader/frontend
Shekhar Vaidya d562bf8d0e fix(frontend): Windows 10 lifecycle text/badge were stale (dated Oct 2025, now Aug 2026)
Homepage's featured card said "Security support until October 2025" --
that date has already passed, so it read as a future deadline that
wasn't. Updated to reflect actual status (mainstream support ended,
consumer ESU runs through Oct 2026) -- kept tight to match the other
three cards' description length so the grid stays even (the first
draft ran long enough to wrap to 3 lines and grow that one card's
height past its siblings).

Also found products.json still tagged both Windows 10 22H2 variants
(2618, 2378) as "EOL SOON" -- inconsistent with the homepage's own
"EOL"/"END OF LIFE" badge for the same product, and equally stale
for the same reason. products.json's badge field renders verbatim
on the product detail page, so this was live and user-facing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-08-17 23:28:21 +05:30
..
public fix(frontend): Windows 10 lifecycle text/badge were stale (dated Oct 2025, now Aug 2026) 2026-08-17 23:28:21 +05:30
src fix(frontend): Windows 10 lifecycle text/badge were stale (dated Oct 2025, now Aug 2026) 2026-08-17 23:28:21 +05:30
.env.example feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
.gitignore feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
eslint.config.js feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
index.html feat(frontend): add Google Search Console verification meta tag 2026-05-12 20:51:28 +05:30
package.json feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
README.md feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
tsconfig.app.json feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
tsconfig.json feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
tsconfig.node.json feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30
vite.config.ts feat: initial release — Windows ISO Downloader v3 2026-04-10 20:15:46 +05:30

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:

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...
    },
  },
])