Make defineExtensionConfig aware of Vite's mode

[arnaugiralt]

Refactored defineExtensionConfig to be a function (see Vite - Conditional configuration), so it can be aware of Vite's mode (development, production) in order to set up source maps and minification properly.

This needs to be considered as a breaking change, so the major version of the package will need to be updated. This won't require any change in most cases, since the helper is mostly used directly as the argument to Vite's defineConfigmethod, but if someone is using that differently, it will require some modifications.

The following setup (used on the Connect BI Reporter extension) will work without any changes:

// vite.config.js
import { defineExtensionConfig } from '@cloudblueconnect/connect-ui-toolkit/tools/build/vite';
import { defineConfig } from 'vite';

export default defineConfig(defineExtensionConfig({ ... }));

But a setup like the following won't:

// vite.config.js
import { defineExtensionConfig } from '@cloudblueconnect/connect-ui-toolkit/tools/build/vite';
import { defineConfig } from 'vite';

export default defineConfig({
  {
    a: { different: { setup: true } } },
  },
  ...defineExtensionConfig({ ... }),
});

It will need to be updated to call defineExtensionConfigwith Vite's mode:

// vite.config.js
import { defineExtensionConfig } from '@cloudblueconnect/connect-ui-toolkit/tools/build/vite';
import { defineConfig } from 'vite';

export default defineConfig((configEnv) => ({
  {
    a: { different: { setup: true } } },
  },
  ...defineExtensionConfig({ ... })(configEnv),
}));

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
82.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud