chore(deps): update concurrently to newer version

[wing328]

Summary by cubic

Upgrade concurrently to v10 and switch the generator CLI and tests to its named export. Updated Jest config to transform concurrently so ESM imports work and tests pass.

• Dependencies

  • Bump concurrently to ^10.0.0 with transitive updates: chalk@5.6.2, supports-color@10.2.2, shell-quote@1.8.4, yargs@18.0.0.

• Migration

  • Requires Node 18+ for scripts using concurrently (via yargs@18/string-width@7).
  • If using Jest, add concurrently to transformIgnorePatterns (done here).

^{Written for commit 5a2bc9d. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[cubic-dev-ai]

1 issue found across 4 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="apps/generator-cli/src/app/services/generator.service.spec.ts">

<violation number="1" location="apps/generator-cli/src/app/services/generator.service.spec.ts:3">
P0: The mock factory wraps `concurrently` inside a module object `{ concurrently: jest.fn() }`, but the test variable `concurrently` is assigned via `jest.mocked(require('concurrently'))` which returns the entire module exports (the object), not the function itself. Calling `concurrently.mockImplementation(...)` then throws because `mockImplementation` does not exist on the wrapper object, only on the jest.fn inside it. Every test that relies on `concurrently.mockImplementation` will fail at runtime.</violation>
</file>

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

P0: The mock factory wraps concurrently inside a module object { concurrently: jest.fn() }, but the test variable concurrently is assigned via jest.mocked(require('concurrently')) which returns the entire module exports (the object), not the function itself. Calling concurrently.mockImplementation(...) then throws because mockImplementation does not exist on the wrapper object, only on the jest.fn inside it. Every test that relies on concurrently.mockImplementation will fail at runtime.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At apps/generator-cli/src/app/services/generator.service.spec.ts, line 3:

<comment>The mock factory wraps `concurrently` inside a module object `{ concurrently: jest.fn() }`, but the test variable `concurrently` is assigned via `jest.mocked(require('concurrently'))` which returns the entire module exports (the object), not the function itself. Calling `concurrently.mockImplementation(...)` then throws because `mockImplementation` does not exist on the wrapper object, only on the jest.fn inside it. Every test that relies on `concurrently.mockImplementation` will fail at runtime.</comment>

<file context>
@@ -1,12 +1,17 @@
 import { Test } from '@nestjs/testing';
+
+jest.mock('concurrently', () => ({
+  concurrently: jest.fn(() => ({
+    result: Promise.resolve([]),
</file context>