Cloud Commander 18.0.0 fails on Node.js 22 with TypeError: validateArgs is not a function

[jorgeoroz]

Environment

• Cloud Commander: 18.0.0
• Node.js: 22.23.1
• npm: 10.9.8
• Operating system: Ubuntu Server

Symptom

Cloud Commander exits during startup:

TypeError: validateArgs is not a function

Reproduction
npm install -g cloudcmd@18.0.0
cloudcmd --no-open
Relevant code
const validateArgs = await simport('@putout/cli-validate-args');

In the tested environment, the returned value is a module object rather than the callable named export.

Workaround

Changing the import to the named export resolves the startup failure:

const {validateArgs} = await import('@putout/cli-validate-args');
Expected result

Cloud Commander should resolve and invoke the validateArgs function consistently on supported Node.js versions.

Additional context

Version 18.0.0 was evaluated as an offline-compatible alternative because later browser assets may depend on external runtime module delivery.

A documented and reversible workaround is available here:

https://github.com/jorgeoroz/cloudcmd-offline-fix

[coderaiser]

Try to use Cloud Commander v19

[jorgeoroz]

Thanks. I initially tested v19, but in this environment outbound access to https://esm.sh is blocked by the corporate network.

As a result, some browser-side functionality fails due to external runtime module imports.

That is why I evaluated v18.0.0 as an offline-compatible fallback and encountered the validateArgs is not a function startup error.

The workaround documented in the issue restores v18.0.0 startup successfully on Node.js 22.23.1.

Would you consider either:

1. providing a fully self-contained/offline build for v19, or
2. removing the external runtime dependency on esm.sh?

That would make v19 usable in restricted and air-gapped enterprise environments.

[coderaiser]

PR’s are welcome

[jorgeoroz]

PR submited
#469