Nx generates invalid names for remote projects with multi-word names

[stacho91]

Current Behavior

When creating a new remote project with a multi-word name using the Nx CLI (as the --name argument), regardless of the notation used (camelCase, underscore, or dot notation), Nx generates a hyphenated name, leading to a validation conflict.

nx g @nx/react:remote --name=myRemote --directory="apps/myRemote" --dynamic=true

NX Generating @nx/react:remote

✔ Which stylesheet format would you like to use? · none
✔ Which E2E test runner would you like to use? · none
✔ Which bundler do you want to use to build the application? · webpack
✔ What should be the project name and where should it be generated? · myRemote @ apps/myRemote

NX Invalid remote name provided: my-remote. The name can only contain letters, digits, underscores, and dollar signs.

Expected Behavior

The Nx CLI should correctly handle multi-word names for remote projects, generating valid names regardless of the notation used.

GitHub Repo

No response

Steps to Reproduce

1. Install the latest Nx CLI using npm install -g nx
2. Generate a new workspace with npx create-nx-workspace@latest
3. Attempt to generate a new 'remote' project with a multi-word name, like so:
   nx g @nx/react:remote --name=myRemote --directory="apps/myRemote" --dynamic=true

Nx Report

Node           : 18.19.0
OS             : darwin-arm64
Native Target  : aarch64-macos
npm            : 10.8.3

nx (global)        : 19.7.3
nx                 : 19.7.3
@nx/js             : 19.7.3
@nx/jest           : 19.7.3
@nx/linter         : 19.7.3
@nx/eslint         : 19.7.3
@nx/workspace      : 19.7.3
@nx/cypress        : 19.7.3
@nx/devkit         : 19.7.3
@nx/eslint-plugin  : 19.7.3
@nx/react          : 19.7.3
@nrwl/tao          : 19.7.3
@nx/web            : 19.7.3
@nx/webpack        : 19.7.3
typescript         : 5.5.4

Failure Logs

No response

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.