Skip to content

Repo: release script breaks on call to yargs.version(false) #8220

@JoshuaKGoldberg

Description

@JoshuaKGoldberg

Suggestion

From our private automations:

/home/runner/work/private-automations/private-automations/typescript-eslint/tools/release/release.mts:10
  .version(false)
   ^

TypeError: yargs.version is not a function
    at <anonymous> (/home/runner/work/private-automations/private-automations/typescript-eslint/tools/release/release.mts:10:4)
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
    at async loadESM (node:internal/process/esm_loader:91:5)
    at async handleMainPromise (node:internal/modules/run_main:65:12)

I'd previously fixed this locally by changing it to yargs(process.argv.slice(2) per https://yargs.js.org/docs/#api-reference.

James noted this did previously work in a test release from the private automations repo. It never worked for me locally. So I'm confused. Maybe I only tried locally in .mts, which maybe has different import semantics?

Metadata

Metadata

Labels

accepting prsGo ahead, send a pull request that resolves this issuebugSomething isn't workingrepo maintenancethings to do with maintenance of the repo, and not with code/docs

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions