Should upgrade cli command update vite.config?

[mddragnev]

There might be some cases where we have trial package handling inside the vite config. For example:

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

When using ig upgrade-packages do you think that the cli should upgrade those references as well or is this a not so common edge case which we should not handle?

[mddragnev]

@damyanpetev @Lipata @dkamburov

[github-actions[bot]]

There has been no recent activity and this issue has been marked inactive.

[dkamburov]

I think those references should be updated by the schematics as well.

[damyanpetev]

I think those references should be updated by the schematics as well.

Yup, would be a nice to check that file and update just in case, but also especially if those are baked into the setup of the CLI projects as well? Which I think might need to be the case since those were needed to have those themes work property when app is built, right?

[github-actions[bot]]

There has been no recent activity and this issue has been marked inactive.