chore(devextreme-vue): replace gulp by nx

[chaosmirage]

Related to #31460, it should be merged first.

[Copilot]

Pull Request Overview

This pull request introduces a new nx-infra-plugin package to replace Gulp-based build scripts with Nx executors for DevExtreme wrapper packages (React and Vue). The changes modernize the build infrastructure by:

• Creating a custom Nx plugin with 8 executors for common build tasks
• Migrating devextreme-react and devextreme-vue packages from Gulp to Nx executors
• Removing Gulp dependencies and associated build configuration files
• Standardizing build processes across wrapper packages

Key Changes

• New nx-infra-plugin package with executors for component generation, TypeScript compilation, file operations, and npm packaging
• Migration of devextreme-react and devextreme-vue from Gulp-based builds to declarative Nx project.json configurations
• Removal of legacy build files (gulpfile.js, build.config.js) and Gulp dependencies

Reviewed Changes

Copilot reviewed 60 out of 61 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tools/scripts/build-nx-plugin.ts	Bootstrap script to compile the nx-infra-plugin before first use
packages/nx-infra-plugin/src/executors/*	8 executor implementations with schema definitions and E2E tests
packages/nx-infra-plugin/src/utils/*	Shared utilities for path resolution, file operations, and error handling
packages/nx-infra-plugin/package.json	Package configuration with dependencies (glob, rimraf) and build scripts
packages/devextreme-react/project.json	Migrated from Gulp to Nx executors with 10+ build targets
packages/devextreme-vue/project.json	Migrated from Gulp to Nx executors with similar target structure
packages/devextreme-react/package.json	Removed Gulp dependencies, added nx-infra-plugin workspace dependency
packages/devextreme-vue/package.json	Removed Gulp dependencies, updated scripts to use Nx
pnpm-lock.yaml	Updated lockfile reflecting dependency changes

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[Copilot]

Pull Request Overview

Copilot reviewed 17 out of 20 changed files in this pull request and generated 4 comments.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (1)

packages/nx-infra-plugin/src/executors/generate-components/executor.ts:265

• Corrected spelling of 'excplicitIndexInImports' to 'explicitIndexInImports'.

[Copilot]

Pull Request Overview

Copilot reviewed 18 out of 21 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[Copilot]

Pull Request Overview

Copilot reviewed 24 out of 27 changed files in this pull request and generated 3 comments.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (1)

packages/nx-infra-plugin/src/executors/generate-components/executor.ts:265

• Spelling error: "excplicitIndexInImports" should be "explicitIndexInImports" (missing 'i'). This matches the same typo in framework-handlers.ts and needs to be corrected for consistency.

[Copilot]

Pull Request Overview

Copilot reviewed 24 out of 27 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

[Copilot]

Pull Request Overview

Copilot reviewed 24 out of 27 changed files in this pull request and generated no new comments.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (2)

packages/nx-infra-plugin/scripts/build.ts:206

• The change from process.exit(0) to process.exit(1) on build failure is a breaking change. The old error handling strategy allowed the process to continue (exit code 0) with the expectation that "The plugin will be built on first use by NX". However, now the postinstall script in package.json will fail on error, which could break package installation. Consider whether this is the intended behavior or if the postinstall script should handle failures gracefully (e.g., using || true or proper error handling).
  packages/nx-infra-plugin/src/executors/generate-components/executor.ts:265
• Typo in property name: excplicitIndexInImports should be explicitIndexInImports (missing 'i'). This inconsistency will cause runtime errors as the schema and project.json use explicitIndexInImports but the code uses the misspelled version.