Skip to content

Instantly share code, notes, and snippets.

@jwmatthews
Last active April 29, 2026 19:03
Show Gist options
  • Select an option

  • Save jwmatthews/3df667ed70aec06ddb64db85c421f73b to your computer and use it in GitHub Desktop.

Select an option

Save jwmatthews/3df667ed70aec06ddb64db85c421f73b to your computer and use it in GitHub Desktop.
Semver Analyzer Tips + Debugging

corepack enable

Running on 2 laptops, Laptop #1 all runs fine, Laptop #2 shows below error. Looks like at some point I ran a corepack enable on Laptop #1 in the specific node version from nvm being used, then on Laptop #2 while I ran corepack enable it was NOT in the right node version used by nvm when semver invoked it.

 source ~/.nvm/nvm.sh && nvm exec 20.11.0 bash -c 'export NODE_ENV=development && yarn install && npx gulp buildPatternfly'
Running node v20.11.0 (npm v10.2.4)
error This project's package.json defines "packageManager": "yarn@4.10.3". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
  • Fix was to run: $ source ~/.nvm/nvm.sh && nvm exec 20.11.0 bash -c 'export NODE_ENV=development && corepack enable'

brew install expect

  • brew install expect

If you don't have "unbuffer" present you will get an error like below

   ./run.sh: line 57: unbuffer: command not found 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment