fix: Add vite.config.ts support to upgrade-packages command

[Copilot]

Fixes #1388 - The ig upgrade-packages command now correctly updates trial package references to licensed package references in vite.config.ts files for React and WebComponents projects.

Problem

When using ig upgrade-packages, the CLI would upgrade package references in TypeScript/TSX files, CSS files, HTML files, and package.json files, but would skip vite.config.ts files. This meant that references like:

export default defineConfig(({ mode }) => {
  return {
    plugins: [
      viteStaticCopy({
        targets: [
          {
            src: "node_modules/igniteui-webcomponents-grids/grids/themes/light/bootstrap.css",
            dest: "themes",
          },
        ],
      }),
    ],
  };
});

Would not be upgraded to use the licensed package paths:

src: "node_modules/@infragistics/igniteui-webcomponents-grids/grids/themes/light/bootstrap.css",

Solution

Added vite.config.ts files to the logic files collection that gets processed during the upgrade for React and WebComponents projects. The existing regex patterns that handle import statement upgrades also correctly handle the string literal paths in vite.config.ts files.

Changes

• packages/core/update/Update.ts: Added 6 lines to include vite.config.ts files in the upgrade process for React and WebComponents frameworks
• spec/unit/update-spec.ts: Added comprehensive tests for both React and WebComponents vite.config.ts upgrade scenarios and updated existing test expectations

Testing

• ✅ Added specific tests for vite.config.ts upgrade functionality for both React and WebComponents
• ✅ All existing updateWorkspace tests continue to pass
• ✅ No regressions introduced - same test failure count as before (unrelated environment issues)
• ✅ Verified that existing regex patterns correctly handle vite.config.ts string literals

The fix is minimal and surgical, leveraging the existing upgrade infrastructure while extending support to an important configuration file used in modern Vite-based projects.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• www.google-analytics.com
  • Triggering command: Ignite UI CLI (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[coveralls]

coverage: 70.204% (+0.04%) from 70.167%
when pulling 89b1f81 on copilot/fix-5858b022-0978-40f0-9ad3-7b3888cfbae8
into d71af0d on master.

[Lipata]

Closing, because the fix is already in #1408