npx "Repository not found" error about kirbyup HOT 3 CLOSED

Seems like this is a npx problem, specific to Windows. You're using Windows, right? Which Node and npm version? Unfortunately, I don't have a fix, since the bug isn't part of kirbyup itself.

To prevent security and user-experience problems from mistyping package names, npx prompts before installing anything. The -y or --yes option just prevents this "do you want to install this package" prompt.

Please use the following package.json instead:

{
  "scripts": {
    "dev": "kirbyup src/index.js --watch",
    "build": "kirbyup src/index.js"
  },
  "devDependencies": {
    "kirbyup": "^0.17.1"
  }
}

from kirbyup.

Thank you for getting back!
I use Mac Big Sur, Node 14.17 and NPM 6.14.

Your setup is missing the npx at the beginning of both commands, but otherwise works! Thanks!

{
  "scripts": {
    "dev": "npx kirbyup src/index.js --watch",
    "build": "npx kirbyup src/index.js"
  },
  "devDependencies": {
    "kirbyup": "^0.17.1"
  }
}

from kirbyup.

I see. How unfortunate the Git error is present on macOS as well...

As stated in the readme's requirements:

ℹ️ When using kirbyup with npx, npm 7+ is required. Previous versions don't pass CLI arguments to the package invoked. npm 7 is bundled from Node 16 onwards.

The setup posted above works as expected. Using npx in conjunction with npm install would defeat the intrinsic purpose of npx. However, if you use npx you can drop the dev dependencies package key all together.

Glad to hear it's working now!

from kirbyup.