Running the cli in Windows results in a crash about typoas

[rjgotten]

Seems like NPM doesn't like when JS files are at top level in the bin field in package.json 😢

Not actually the problem. Top-level JS files are just fine.
The problem is that the package doesn't have an #!/usr/bin/env node moniker in the ./lib/bin.js file referred to by the bin field. Entries in the bin field require that moniker to instruct the tooling that they should use Node.JS to execute the files rather than try to run them directly. The NPM docs on the bin field literally state:

Please make sure that your file(s) referenced in bin starts with #!/usr/bin/env node, otherwise the scripts are started without the node executable!

Having the bin field top-level does introduce another problem though. A top-level bin field will generate command proxies in the node_modules/.bin folder that use the bare (!!) package name. I.e. the command you are creating won't be @typeoas/cli. It'll just be cli. Which has very poor discoverability.

Would recommend using

"bin" : { "typeoas-cli" : "./lib/bin.js" }

[Embraser01]

Hi,

Seems like NPM doesn't like when JS files are at top level in the bin field in package.json 😢
In the mean time, Yarn or pnpm are both working as expected.

Will mark this as a bug and try for a fix

[Embraser01]

Thank you for your help. I released a new version with the fix. From my testing, it should work now except for the following case:
When running npx inside an existing project, it fails with:

> Run npx @typoas/cli generate -i https://petstore3.swagger.io/api/v3/openapi.json -o test.ts
'typoas-cli' is not recognized as an internal or external command,
operable program or batch file.
> Error: Process completed with exit code 1.

I'm also adding some E2E tests to be sure.

[Embraser01]

Seems that it only fail in the typoas repo on Windows (maybe related to npm/cli#6276) , I'm gonna close this