typescript-fetch: install tsc in the workflow

Merged
WI
1d ago
+3-0

to fix

npm warn deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm warn deprecated @types/form-data@2.5.0: This is a stub types definition. form-data provides its own type definitions, so you do not need this installed.
npm error code 127
npm error path /home/runner/work/openapi-generator/openapi-generator/samples/client/petstore/typescript-fetch/builds/with-npm-version
npm error command failed
npm error command sh -c npm run build
npm error > @openapitools/typescript-fetch-petstore@1.0.0 build
npm error > tsc && tsc -p tsconfig.esm.json
npm error sh: 1: tsc: not found
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-11-17T18_55_48_372Z-debug-0.log

PR checklist

  • Read the contribution guidelines.
  • Run the following to build the project and update samples:
    ./mvnw clean package || exit
    ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
    ./bin/utils/export_docs_generators.sh || exit
    
    (For Windows users, please run the script in WSL)
    Commit all changed files.
    This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
    These must match the expectations made by your contribution.
    You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
    IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.