Repository navigation
Releases: loathers/create-kolmafia-script
Releases · loathers/create-kolmafia-script
Release list
v0.4.0
Breaking
- Node
^22.20 || ^24.10 || >= 25is now required, up from 20.11. Node 20 and 23 are both past end of life. - Turn switches off with
--no-libram.--libram=falseis now rejected rather than quietly ignored, which is what it did before — you would ask for no libram and get libram. - A project is named after the last segment of its path, so
create-kolmafia-script nest/innerproduces a package calledinner.
Added
--node-pmto choose the package manager, optionally with an exact version, as in--node-pm pnpm@11.22.0. npm and pnpm work; yarn remains the best tested. (#15)- Generated projects come with a GitHub workflow that builds, lints and deploys to a
releasebranch. Opt out with--no-setup-github. (#13) --version.
Fixed
- Package manager commands run inside the new project. They were passing
--cwdwhile running from wherever you invoked them, and corepack resolvespackageManagerfrom the process directory, so every install silently used Yarn Classic 1.22 instead of the project's Yarn 4. (#8, #10) - Your global
~/.yarnrcis no longer written to. Configuring the new project used Yarn Classic'sconfig set, which only ever writes to your home directory, so the setting landed on your account and never on the project. - Git user is read from included config files. Looking only at the global file skips
includedirectives, so anyone keeping their name and email in an included file got placeholders. (#11) - The generated script compiles to something KoLmafia can run. The template called
console.log, which does not exist there. It now usesprintfromkolmafia. (#12) - Piping into the CLI no longer crashes. With no terminal to prompt in it used to die inside readline; it now takes the defaults.
--installworks on Windows. It asked for a path and then read a different variable, so it rejected every answer..gitignorereaches new projects. npm strips the file from published tarballs. (#14)- Boolean flags work at all.
yargs-interactivepassed its own option types through to yargs, which has never heard ofconfirm, so nothing was ever coerced and--libram=falsearrived as a truthy string.
Internal
yargs-interactive, last published in 2022 and pinning inquirer 7 and yargs 14, is replaced by @clack/prompts and pargs. The project also picked up vitest, eslint, typechecking and CI along the way.
